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.
git clone --depth 1 https://github.com/landim32/awesome-ai-skillsWrote 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/commands/landim32/awesome-ai-skills/speckit.analyze)<a href="https://agentmods.dev/commands/landim32/awesome-ai-skills/speckit.analyze"><img src="https://agentmods.dev/badge/commands/landim32/awesome-ai-skills/speckit.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/commands/landim32/awesome-ai-skills/speckit.analyze"><img src="https://agentmods.dev/badge/commands/landim32/awesome-ai-skills/speckit.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.00026 | $0.01615 |
| Opus 5 | $0.00013 | $0.00807 |
| Sonnet 5 | $0.00005 | $0.00323 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade A, and why
speckit.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 11d 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.
This is a copy
86% identical to speckit.analyze — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Goal
Identify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts (spec.md, plan.md, tasks.md) before implementation. This command MUST run only after /speckit.tasks has successfully produced a complete tasks.md.
Operating Constraints
STRICTLY READ-ONLY: Do not modify any files. Output a structured analysis report. Offer an optional remediation plan (user must explicitly approve before any follow-up editing commands would be invoked manually).
Constitution Authority: The project constitution (.specify/memory/constitution.md) is non-negotiable within this analysis scope. Constitution conflicts are automatically CRITICAL and require adjustment of the spec, plan, or tasks—not dilution, reinterpretation, or silent ignoring of the principle. If a principle itself needs to change, that must occur in a separate, explicit constitution update outside /speckit.analyze.
Execution Steps
1. Initialize Analysis Context
Run .specify/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks once from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Derive absolute paths:
- SPEC = FEATURE_DIR/spec.md
- PLAN = FEATURE_DIR/plan.md
- TASKS = FEATURE_DIR/tasks.md
Abort with an error message if any required file is missing (instruct the user to run missing prerequisite command). For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").
2. Load Artifacts (Progressive Disclosure)
Load only the minimal necessary context from each artifact:
From spec.md:
- Overview/Context
- Functional Requirements
- Success Criteria (measurable outcomes — e.g., performance, security, availability, user success, business impact)
- User Stories
- Edge Cases (if present)
From plan.md:
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.
- 11d ago First seen · 185 lines · 26 tokens per session scan A 878794d6a6e3
speckit.analyze is a command published in the GitHub repository landim32/awesome-ai-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 1,615 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to speckit.analyze, differing in 8 lines, and is treated as a copy.
Other commands, from other repositories
skill-safety
Hostile audit of coding-agent configuration the project installed rather than wrote: skills, subagents, commands, plugins, hooks, and rule files obtained from a marketplace, a git URL, a gist, or a teammate. Assume every installed instruction file is attacker-authored until read, and that the attacker's goal is to be…
cr
Tool-driven implementation of unresolved PR/MR review comments on GitHub, GitLab or Bitbucket: fetch every comment thread plus the out-of-thread notices (review bodies, bot summaries), evaluate each for technical validity, implement valid ones one at a time with a full validation pass after each, and scan the codebase…
_conventions
Read this file before executing any command file. Every rule here applies to every command unless the command file explicitly overrides it.
reliability
Hostile audit of behavior when a dependency fails, a call is retried, or a message is redelivered: assume every retry double-applies, every external call hangs forever, and every crash lands in the worst window — then prove where. A call that is idempotent, bounded, timed-out, and backed-off survives; anything else is…
agent-rules
Audits the project's agent rule configuration end-to-end: validates every rule file, classifies every rule in the root instruction file as correctly placed or misplaced, and generates concrete new-rule suggestions from audit artifacts and project conventions. Assume every rule file has defects until proven otherwise.
cache
Hostile audit of caching correctness: assume every cache serves stale data after a write, shares a key across entities that must not share one, grows without bound, and stampedes on expiry — then prove where. A cache is a correctness liability until its key, its invalidation, its bound, and its expiry behavior are all…