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/implementnpx skills add andyrids/icm-spec --skill implementgit clone --depth 1 https://github.com/andyrids/icm-specWhat 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.00019 | $0.00199 |
| Opus 5 | $0.00010 | $0.00100 |
| Sonnet 5 | $0.00004 | $0.00040 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
implement 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 yesterday.
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
ICM stage 02 - implementation
The argument names the plan slug. If it is empty, use the single status: in-progress or
status: planned plan in plans/; if that is ambiguous, ask which slug to run.
- Read
ICM/process-plan/stages/02-implementation/CONTEXT.md. If it is missing, stop and suggest/icm:init. - Execute the stage contract exactly as written, working from
ICM/process-plan/stages/01-specification/output/<slug>-spec.mdand the plan's Approach. - Stop at the workspace's review gate: present the implementation report for explicit user
acceptance.
/icm:verifyis the next step once accepted.
$ARGUMENTS
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.
- yesterday First seen · 20 lines · 19 tokens per session scan A 9ae81ab9a688
implement is a skill published in the GitHub repository andyrids/icm-spec (2 stars, last pushed 13d ago), licensed Apache-2.0. It adds 19 tokens to every session and 199 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"…
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.
model-compatibility
Model family compatibility matrix covering loaders, resolutions, samplers, CFG, VAE, ControlNet, and LoRA compatibility for SD 1.5, SDXL, Flux, SD3, and video models.