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/andyrids/icm-spec/plannpx skills add andyrids/icm-spec --skill plangit clone --depth 1 https://github.com/andyrids/icm-specWrote 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/andyrids/icm-spec/plan)<a href="https://agentmods.dev/skills/andyrids/icm-spec/plan"><img src="https://agentmods.dev/badge/skills/andyrids/icm-spec/plan.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.00026 | $0.00394 |
| Opus 5 | $0.00013 | $0.00197 |
| Sonnet 5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
plan 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.
What it actually says
Working under plans/
plans/ is the planning system - one file per unit of work, frozen at status: done as the
durable record. The full protocol, frontmatter contract and closeout steps are
plans/README.md. Read it before writing.
The rules that bite most often:
- Frontmatter is queried, so it must stay exact:
statusis one ofplanned | in-progress | done | blocked | cancelled;specs:andauthors:paths must resolve; the Layer 4 hierarchy keys are present. - The two spec fields answer different questions.
specs:means this plan brings code into conformance and stage 03 verifies against it;authors:means this plan writes the spec and changes no behaviour. One field, never both - over-listingspecs:silently defeats the coverage invariant, which is how it died the first time. - Body section order is fixed: Scope, Implements, Approach, Validation, Risks / unknowns, Notes,
Follow-ups. Validation supplies the requirement identifiers stage 03 reports against, and its
criteria are written in EARS (
ICM/_config/reference-standard-validation.md). - At closeout, tick a Validation box only where evidenced; an unticked box with a reason in Notes beats a ticked one that was never checked.
- A
Deferred tofollow-up edits the named downstream plan in the same commit, or the work is lost between two documents.
Plans are opened by ICM stage 01 (/icm:specify) and frozen by stage 04 (/icm: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.
- 4d ago First seen · 33 lines · 26 tokens per session scan A 054abc8ff595
plan is a skill published in the GitHub repository andyrids/icm-spec (2 stars, last pushed 16d ago), licensed Apache-2.0. It adds 26 tokens to every session and 394 once invoked, about $0.0001 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
tldr
Generate a review-oriented TLDR of GitHub Spec Kit artifacts (spec.md and/or plan.md) as a self-contained HTML dashboard plus a Markdown version, to make reviewing those files in a pull request faster. Use this skill whenever the user wants to review, summarize, "TLDR", skim, or get an overview of a Spec Kit spec.md…
tldr-delete
Remove generated speckit-tldr output — the .tldr.html and .tldr.md files and the specs/ /tldr/ directories that hold them — so these local review artifacts are not committed into a pull request. Use this skill whenever the user wants to delete, remove, clean, clear, or "clean up" the TLDRs that the tldr skill…
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
conductor-implement
Executes the tasks defined in the specified track's plan. Use this to start or continue working on a feature, bug fix, or chore.
ideogram-ultra
Build Ideogram 4 (Ideogram Ultra) txt2img and img2img workflows with the local open-weights model, dual conditional/unconditional models with DualModelGuider, Qwen3-VL text encoder, and structured JSON ("compositional deconstruction") prompts for strong text rendering and layout control.