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 agents/eight-acres-lab/openmelon/speckit.analyzegit clone --depth 1 https://github.com/eight-acres-lab/openmelonWrote 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/agents/eight-acres-lab/openmelon/speckit.analyze)<a href="https://agentmods.dev/agents/eight-acres-lab/openmelon/speckit.analyze"><img src="https://agentmods.dev/badge/agents/eight-acres-lab/openmelon/speckit.analyze.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 | $0.00026 | $0.01614 |
| 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 5d 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.
Copies of this mod
7 near-identical copies found in the catalogue:
- speckit.analyze — 100% identical, 0 lines differ
- speckit.analyze — 89% identical, 8 lines differ
- speckit.analyze — 89% identical, 8 lines differ
- speckit.analyze — 86% identical, 6 lines differ
- speckit.analyze — 86% identical, 6 lines differ
- speckit.analyze — 86% identical, 6 lines differ
- speckit.analyze — 86% identical, 6 lines differ
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/bash/check-prerequisites.sh --json --require-tasks --include-tasks 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:
- Architecture/stack choices
- Data Model references
- Phases
- Technical constraints
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.
- 5d ago First seen · 185 lines · 26 tokens per session scan A 0dd76be34a60
speckit.analyze is an agent published in the GitHub repository eight-acres-lab/openmelon (86 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,614 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-30.
Other agents, from other repositories
reviewer-test-coverage
Review code changes for missing tests, untested edge cases, and test quality.
reviewer-code-quality
Review code changes for bugs, logic errors, edge cases, and code smells.
streaming
Streaming is key to building responsive applications. There are a few types of data you’ll want to stream.
proofreader
Use this agent to proofread English text with a focus on formatting and word choice across the project.
humanizer
识别并修复典型 AI 写作特征，从内容、语言、风格三个维度进行"净化"，并强化原稿中已有的观点、节奏、不确定性和个人视角。Humanizer 只改表达，不创造事实、经历或证据。包含严格的黑名单过滤和 50 分制质量自评。.
wechat-reader-test
多平台读者压力测试器（保留 wechat-reader-test 名称以兼容既有工作流）。 从 01theme.md 读取发布平台，为公众号、今日头条、知乎选择不同的定性测试矩阵； 不伪造 CTR、完读率或推荐量预测。由工作流导演在 Stage 9 显式调用。.