메뉴
Visualize subagent, Agent tool, and delegated task activity from the current Claude Code session. Use when work was delegated or the user asks what agents/subagents did, what ran in the background, or how tasks were coordinated.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | agents |
| description | Visualize subagent, Agent tool, and delegated task activity from the current Claude Code session. Use when work was delegated or the user asks what agents/subagents did, what ran in the background, or how tasks were coordinated. |
| allowed-tools | ["Bash","Read","Agent"] |
node "${CLAUDE_PLUGIN_ROOT}/scripts/run-artilens.mjs" session agents --data .claude/artilens/agents.data.json.subagent_type: general-purpose, model: sonnet, run_in_background: true. Prompt template:
"Read <absolute path to agents.data.json> and ${CLAUDE_PLUGIN_ROOT}/references/artifact-authoring.md. Load the artifact-design skill, then author and publish an artifact with the Artifact tool.
Page plan: timeline of which subagent did what and when; a task/result summary table. Copy-as-prompt is optional — only include it if the JSON has editable state worth capturing.
All visual design decisions are yours."If hook event logging is enabled, the data JSON includes richer SubagentStart/SubagentStop and Task events.
List, find, inspect, diff, resume, or update this project's locally registered artifacts. Use when the user references a previous artifact, asks what artifacts exist, wants artifact history, or wants to continue from an artifact.
Create a draggable planning, kanban, roadmap, or backlog board artifact with copy-as-prompt feedback. Use for task ordering, project boards, sprint planning, prioritization, or moving cards between columns.
Catalog available slash commands, ArtiLens skills, plugins, and contextual recommendations. Use when the user asks what commands/tools/skills are available, what ArtiLens can do, or what to run next.
Create an option comparison artifact with tradeoffs and a recommendation. Use when the user wants to compare approaches, architectures, libraries, plans, implementation choices, pros/cons, or decision options.
Inventory project context files — CLAUDE.md, AGENTS.md, rules, SKILL.md files, plans, and docs — with read-frequency from the current transcript. Use when the user asks what context is loaded, which files shaped the session, or before auditing stale or unused context files.
Create a dependency review artifact from real package metadata. Use when checking dependencies, package.json, outdated or deprecated packages, license risk, upgrade order, dependency health, or version cleanup.