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 cdeust/ai-architect-mcp-spec --skill validate-specgit clone --depth 1 https://github.com/cdeust/ai-architect-mcp-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/cdeust/ai-architect-mcp-spec/validate-spec)<a href="https://agentmods.dev/skills/cdeust/ai-architect-mcp-spec/validate-spec"><img src="https://agentmods.dev/badge/skills/cdeust/ai-architect-mcp-spec/validate-spec.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.1 | $0.00066 | $0.00246 |
| Opus 5 | $0.00033 | $0.00123 |
| Sonnet 5 | $0.00013 | $0.00049 |
| Haiku 4.5 | $0.00007 | $0.00025 |
Grade A, and why
validate-spec 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 8d 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
Validate a specification section
Use the prd-spec-verifier MCP server for a focused structural check.
Workflow
- Read the section without rewriting it.
- Select the closest
section_typeaccepted by thevalidate_prd_sectiontool schema. Ask for clarification if the section's role is ambiguous. - Call
validate_prd_sectionwith the exact content and selected type. - Report rule identifiers, severities, evidence, and the returned score. Separate violations from checks that passed.
- State the scope limit: the validator checks implemented formatting, traceability, and consistency rules. It does not prove that claims are true, requirements are desirable, code exists, or the design is feasible.
Do not infer semantic correctness from a zero-violation result. Do not edit the section unless the user asks for a revision.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 19 lines · 66 tokens per session scan A c193e86164ee
validate-spec is a skill published in the GitHub repository cdeust/ai-architect-mcp-spec (3 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 246 once invoked, about $0.0003 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
adeu-redlining
Use this skill when reviewing, editing, redlining, or negotiating an existing Microsoft Word document (.docx) — including proposing edits as tracked changes, accepting or rejecting existing tracked changes, replying to comments, comparing two versions, sanitizing author metadata, or finalizing a contract for…
lain
Structural code intelligence for AI coding agents. Use this skill when the user wants to understand how a codebase is organized (modules, call graphs, file dependencies), find where to start reading, trace the impact of a change, find code by meaning, or understand what a symbol does in its full context. Do NOT use…
wiki
Rebuild a flow-first project wiki using the mimirs wiki MCP tool. Use when the user asks to generate, rebuild, refresh, or write the wiki for a codebase.
plan
Design an implementation plan before writing code — where the change lands, what it will touch, what could break, and the steps in order. Use when asked to plan a feature, scope a change, or figure out how to approach an edit before making it. To assess a change that already exists (a diff, refactor, or rename), use…
research
Answer a hard, open-ended question about how the project works or is built by synthesizing every source — code, structure, git history, prior decisions, discussion, caveats — and verifying each claim against the source. Use for deep cross-cutting questions that span more than one area. Narrower siblings — a single…
scout
Research the web for solutions, competitors, alternatives, or prior art for a decision facing this project — then store the findings in project memory so they survive the session. Use when choosing a library or approach, comparing tools, checking what others do, or evaluating whether to build vs adopt.