Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/teamspwk/nova/status-dashboardnpx skills add TeamSPWK/nova --skill status-dashboardgit clone --depth 1 https://github.com/TeamSPWK/novaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/teamspwk/nova/status-dashboard)<a href="https://agentmods.dev/skills/teamspwk/nova/status-dashboard"><img src="https://agentmods.dev/badge/skills/teamspwk/nova/status-dashboard.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00113 | $0.01330 |
| Opus 5 | $0.00056 | $0.00665 |
| Sonnet 5 | $0.00023 | $0.00266 |
| Haiku 4.5 | $0.00011 | $0.00133 |
Grade A, and why
status-dashboard scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nova Status Dashboard (STRICT)
너는 /nova:status 호출 시 다음 흐름을 순서대로 강제 실행한다. 자율 해석 금지.
사용자 의도 = Nova 표준 HTML 대시보드 생성. 다른 의도로 우회하지 않는다.
🚫 금지 행동 (Claude 우회 차단)
다음 행동은 사용자 의도 위반이다:
- NOVA-STATE.md만 읽고 텍스트 요약으로 대체 — 사용자는 HTML 요청 (텍스트 답변 X)
- 프로젝트 자체 dashboard 도구로 우회 —
dashboard/build*.py/Makefile dashboard/web/app/status/발견해도 무시 - minimal mode HTML 만들고 멈춤 —
--auto-bootstrap이 자동 진화 강제 - "이런 대안 있어요" 제안하며 멈춤 — Step 1 무조건 실행 후 결과 보고
예외: 사용자가 명시적으로 자체 도구를 요청한 경우.
✅ 실행 흐름 (STRICT)
Step 1: 무조건 실행
nova-status
Claude Code가 플러그인 bin/을 Bash tool PATH에 자동 등록하므로 cwd 무관 작동. bin/nova-status wrapper가 내부적으로 --auto-bootstrap --open 강제.
PATH 미반영(오래된 세션) 폴백: bash "$NOVA_PLUGIN_ROOT/bin/nova-status" — SessionStart hook이 $CLAUDE_ENV_FILE을 통해 export.
Step 2: 결과 분기
JSON mode / minimal |
동작 |
|---|---|
roadmap |
✅ 완료. Phase/Sprint/Drift 1줄 요약 보고 |
phase1 + minimal:false |
✅ Phase 1 호환. plan frontmatter 기반 dashboard 작동 |
phase1 + minimal:true |
→ --auto-bootstrap이 §22 흐름 자동 진입 |
Step 3 (MUST 자동): minimal → 자동 부트스트랩
render-status.sh --auto-bootstrap이 자동 처리하며, stderr에 [CLAUDE_AUTO_CONTINUE] 마커가 출력되면 메인 Claude는 무조건 다음 단계를 단일 응답 내에 자동 수행 (사용자 결정 요청 없음):
init-roadmap.sh --llm자료 수집 (NOVA-STATE + git log + plans) — 자동- Agent(general-purpose) spawn — stderr
[2/3]블록의 prompt 그대로 사용 (사용자 결정 요청 X) - Agent가
/tmp/ROADMAP-{slug}-draft.md작성 (slug =[CLAUDE_AUTO_CONTINUE]의DRAFT_PATH값) render-status.sh --roadmap {DRAFT_PATH} --open --no-bootstrap재실행 — 풍부 모드 HTML 갱신- 자동 commit 0건 — 사용자 검수 후 명시적 commit
🚫 minimal HTML(빈 껍데기)만 사용자에게 보여주고 멈추면 사용자 의도 위반이다. 결과(풍부 모드 dashboard)까지 무조건 자동.
Step 3.5 (SOT 충돌 시): default 자동 선택
stderr 마커 PLAN_COUNT > 0이면 docs/plans/* SOT가 이미 존재. A/B/C 중:
- (A) Plan frontmatter 수정, (B) Plan 마일스톤 ROADMAP 흡수 — 파괴적 → 사용자 결정 영역
- (C) draft 검수 + 임시 풍부 모드 유지 — 자동 default 적용
Claude는 무조건 (C)를 자동 적용해 dashboard 결과를 즉시 제공한다. A/B로 변경하려면 사용자가 명시 요청.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 93 lines · 113 tokens per session scan A a3edbd41dd78
status-dashboard is a skill published in the GitHub repository TeamSPWK/nova (2 stars, last pushed 4d ago), licensed MIT. It adds 113 tokens to every session and 1,330 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
code-overview-to-confluence
Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location. Use when the user wants code or a PR explained, oriented, or made sense of AND the overview posted to a Confluence space or page.…