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 tercel/spec-forge --skill analyzegit clone --depth 1 https://github.com/tercel/spec-forgeWrote 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/tercel/spec-forge/analyze)<a href="https://agentmods.dev/skills/tercel/spec-forge/analyze"><img src="https://agentmods.dev/badge/skills/tercel/spec-forge/analyze/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/tercel/spec-forge/analyze"><img src="https://agentmods.dev/badge/skills/tercel/spec-forge/analyze.svg" alt="Reviewed on agentmods" width="80" 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.00069 | $0.03497 |
| Opus 5.5 | $0.00028 | $0.01399 |
| Sonnet 5.5 | $0.00014 | $0.00699 |
| Haiku 4.5 | $0.00007 | $0.00350 |
Grade A, and why
analyze 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 1mo 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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze — Document Landscape Analysis & Knowledge Mapping
Map, understand, and evaluate a collection of documents as a body of knowledge. Identify structure, themes, gaps, redundancies, conflicts, and staleness. Produce an actionable analysis with reorganization recommendations.
Core Principles
- Landscape-first: Build the map before judging — understand what exists before critiquing
- Theme-driven: Group documents by what they're about, not just where they live
- Conflict detection: Find contradictions between documents that may confuse readers
- Staleness awareness: Identify documents that may be outdated based on content signals
- Non-destructive: Only reads and reports — never modifies source documents
- Reorganization as suggestion: Propose better structures, don't impose them
When to Use Analyze vs. Audit
| Situation | Use |
|---|---|
| Single project with docs/ and source code | /spec-forge:audit |
| Docs-only repo with mixed content | /spec-forge:analyze |
| Cross-repo documentation ecosystem | /spec-forge:analyze |
| Research notes, ideas, decision records | /spec-forge:analyze |
| API docs need checking against code | /spec-forge:audit |
| "I have a mess of docs and need to understand them" | /spec-forge:analyze |
Workflow
Step 1: Determine Scope
Parse the arguments to determine what to analyze:
- If a path argument is provided (e.g.,
/spec-forge:analyze ../../aipartnerup-docs), use that as the root - If no path, use the current working directory's
docs/directory - If multiple paths are provided, analyze all of them as one collection
Use AskUserQuestion to understand the user's goals:
- What is this collection? (e.g., "ecosystem docs for multiple products", "research notes", "mixed specs and decisions")
- What do you want to understand? Options:
- Full landscape analysis (recommended for first time)
- Find conflicts and contradictions
- Find gaps and missing coverage
- Suggest reorganization
- All of the above
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.
- 1mo ago First seen · 411 lines · 69 tokens per session scan A fed1f952d16d
analyze is a skill published in the GitHub repository tercel/spec-forge (10 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 3,497 once invoked, about $0.0003 per session on Opus 5.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
analyzing-architecture
Detects repository context, maps dependencies (enterprise-specific or general), and generates/persists architectural documentation.
board-deck-builder
Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.
architecture-diagram
Build interactive, click-through architecture diagrams for software systems — a self-contained single HTML file with animated step-by-step flows, mode toggles (dev/prod, offline/online, v1/v2), dark/light theme, and a side panel with payload details, plus a companion markdown description. Use when the user wants to…
012-agile-epic
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for…
okf-open-knowledge-format
Create, validate, and enrich Open Knowledge Format (OKF) bundles — the open spec for representing organizational knowledge as markdown files with YAML frontmatter. Use when the user mentions 'OKF', 'Open Knowledge Format', 'knowledge bundle', 'OKF bundle', 'create a knowledge base for agents', 'validate OKF', 'convert…
001-commands-inventory
Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the project root. This should trigger for requests such as Create embedded commands inventory checklist; Generate INVENTORY-COMMANDS-JAVA.md; Use…