Borrowing it
Nothing to install: this file belongs to DeL-TaiseiOzaki/claude-code-orchestra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DeL-TaiseiOzaki/claude-code-orchestra/main/.claude/skills/design-tracker/SKILL.mdgit clone --depth 1 https://github.com/DeL-TaiseiOzaki/claude-code-orchestraWrote 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/del-taiseiozaki/claude-code-orchestra/design-tracker)<a href="https://agentmods.dev/skills/del-taiseiozaki/claude-code-orchestra/design-tracker"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/design-tracker/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/del-taiseiozaki/claude-code-orchestra/design-tracker"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/design-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00071 | $0.01952 |
| Opus 5 | $0.00036 | $0.00976 |
| Sonnet 5 | $0.00014 | $0.00390 |
| Haiku 4.5 | $0.00007 | $0.00195 |
Grade A, and why
design-tracker 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 today.
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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Tracker Skill
Purpose
This skill keeps the project's 要件定義書 (.claude/docs/DESIGN.md) current.
DESIGN.md is the macro requirements & design document (what the project builds
and why); micro work progress lives in PROGRESS.md. It covers:
- Background & purpose, scope
- Functional & non-functional requirements
- Architecture (including agent roles)
- Tech stack choices and their rationale
- Constraints, key decisions, and open questions
How This Skill Is Reached
Read this before relying on it: nothing in the repository activates this skill automatically. The description above is the entire trigger surface, and it works only through the runtime's own description-based skill selection.
- Explicit request — "record this", "add to design", "update DESIGN",
"記録して",
/design-tracker. This is the reliable path. - Model invocation from the description, at the runtime's discretion.
Claude Code discovers the skill through
.claude/skills→.claude/skills; Codex through.codex/config.toml'spath = ".claude/skills/design-tracker". - No hook mechanism.
.claude/hooks/contains no design-tracker branch, and the words a design conversation actually uses (設計 / design / architecture) are claimed byCODEX_TRIGGERSinagent-router.py, which injects a Codex consultation nudge instead.check-codex-before-write.pyalso nudges whenDESIGN.mdis edited, but it blocks nothing — a freehand edit still lands.
So an agent in a design conversation must decide to record the decision; no
automation will decide for it. If a decision was made and this skill was not
reached, record it at the next checkpoint — /checkpointing describes recording
decisions via update_design.py for exactly that reason.
Previous versions of this file promised proactive, automatic activation ("Do NOT wait for user to ask"). That promise was enforced by nothing, so it has been removed rather than left as a false statement in a normative document.
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.
- today Changed 67c83fccba0f
- 5d ago Changed · +1 tokens per session 14ff2e156a86
- 10d ago First seen · 158 lines · 70 tokens per session scan A 8c49138db3c4
design-tracker is a skill published in the GitHub repository DeL-TaiseiOzaki/claude-code-orchestra (195 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 1,952 once invoked, about $0.0004 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.