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 skills add ZhangHanDong/agent-spec --skill agent-spec-intent-compilergit clone --depth 1 https://github.com/ZhangHanDong/agent-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/zhanghandong/agent-spec/agent-spec-intent-compiler)<a href="https://agentmods.dev/skills/zhanghandong/agent-spec/agent-spec-intent-compiler"><img src="https://agentmods.dev/badge/skills/zhanghandong/agent-spec/agent-spec-intent-compiler/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/zhanghandong/agent-spec/agent-spec-intent-compiler"><img src="https://agentmods.dev/badge/skills/zhanghandong/agent-spec/agent-spec-intent-compiler.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 89 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00042 | $0.01767 |
| Opus 5 | $0.00021 | $0.00883 |
| Sonnet 5 | $0.00008 | $0.00353 |
| Haiku 4.5 | $0.00004 | $0.00177 |
Grade A, and why
agent-spec-intent-compiler 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 9d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Spec Intent Compiler
Version: 1.0.0 | Last Updated: 2026-08-14 | Tracks: agent-spec 1.4.0
Use this skill when a user wants to move from raw PRD/issue prose to governed KLL requirements and task specs.
Routing: What You Hold, Where It Goes
Before writing anything, route the artifact. This table copies
knowledge/standards/operational/id-registry.md — the registry is the
authority, this copy is checked against it in CI.
| You hold | Directory | Id prefix | Scaffold |
|---|---|---|---|
| A debate: should we do this, and why | knowledge/proposals/ |
LEP- |
agent-spec knowledge new proposal LEP-NNN |
| A settled architectural ruling | knowledge/decisions/ |
ADR- |
agent-spec knowledge new decision ADR-NNN |
| An obligation the system must satisfy | knowledge/requirements/ |
REQ- |
agent-spec knowledge new requirement REQ-NNN |
| An executable, verifiable task contract | specs/ |
task- |
agent-spec init --level task |
HARD GATE: when the workspace has a knowledge/requirements/ corpus, do NOT
write a task contract without satisfies: [REQ-*] — the orphan-spec lint
diagnoses the jump. "This is just a small task" and "I'll link it later" are
the rationalizations that produced orphan contracts before; route first, then
write.
Rules
- The CLI remains deterministic and model-free.
- Raw source belongs in
docs/. - Machine-consumable truth belongs in
knowledge/requirements/*.md. - Do not silently invent missing requirements. Emit or ask clarification questions.
- Do not treat a model inference as accepted; only human-confirmed answers may change KLL truth.
- Every generated requirement must include
## Source Trace. - Open questions stay in
## Open Questionsuntil answered by the human. - For agent-spec's own development, dogfood this workflow on the repository's own KLL requirement and task spec before presenting fixtures as sufficient proof.
- Treat KLL roots as compiler trust boundaries: do not bypass unsafe-id, strict-frontmatter, kind-directory, missing-root, or symlink diagnostics.
- Read the plan as a cross-layer DAG: requirement nodes lower to work units, work units satisfy spec nodes, and spec dependencies remain explicit edges.
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.
- 9d ago First seen · 157 lines · 42 tokens per session scan A 814f38f19396
agent-spec-intent-compiler is a skill published in the GitHub repository ZhangHanDong/agent-spec (454 stars, last pushed 10d ago), licensed MIT. It adds 42 tokens to every session and 1,767 once invoked, about $0.0002 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
comet-native
A workflow for managing Native changes in Comet, where requirements, progress, and acceptance results are saved in project files. It uses the Comet command-line runtime to move through defined work stages.
comet
Comet — OpenSpec + Superpowers dual-star development workflow. Start with /comet for automatic phase detection and dispatch to subcommands. Five phases: open → design → build → verify → archive.
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session.
comet-hotfix
A quick workflow for fixing an existing bug in Comet, a tool that manages structured code changes. It moves through opening the change, building, checking, and archiving it.
comet-verify
A workflow for verifying a Comet change after its coding tasks are complete. Comet is a tool that tracks structured software changes through stages.
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.