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 commands/oriolshhh/runware-image-mcp/specgit clone --depth 1 https://github.com/Oriolshhh/runware-image-mcpWrote 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/oriolshhh/runware-image-mcp/spec)<a href="https://agentmods.dev/commands/oriolshhh/runware-image-mcp/spec"><img src="https://agentmods.dev/badge/commands/oriolshhh/runware-image-mcp/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.00030 | $0.00992 |
| Opus 5 | $0.00015 | $0.00496 |
| Sonnet 5 | $0.00006 | $0.00198 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec — Create a spec and wait for approval
Purpose
Turn a request into an approved, testable specification before any code.
Invocation
/spec <short description of the work>
Accepted input
A request, problem statement, or ticket, with any links or constraints.
Prerequisites
A HarnessKit workspace (harnesskit init). No approved spec required.
Procedure
- Read
.agent/context/README.mdand routing when present, assess freshness, and inspect task-relevant source. Do not ask questions answered by the repo. - Triage facts, assumptions, preferences, and blockers. If needed, ask one grouped batch of normally at most three questions (absolute maximum five), then wait for the answers. State reasonable defaults for non-blockers.
- Select and announce one path:
direct-specfor small, local, reversible, clear work.specialist-assisted-specfor medium/cross-cutting work needing one to three relevant specialist planning reviews.full-council-specfor high-risk, irreversible, architectural, security- sensitive, or product-contested work. Execute/councilfirst, or consume its already-approved decision record. Applymodel-routing:direct-specmay downgrade to standard/medium; specialist-assisted planning uses each selected agent's declared tier; and full-council planning plus final synthesis remains heavy/high.
- In specialist-assisted mode, use
specialist-routing; issue the same brief and coordinator-built context capsule to the smallest relevant set of agents; tell them to start from the capsule rather than reload the context pack. Collect independent first-pass reports in parallel when native isolated subagents are supported, and otherwise use honestly labelled native- or simulated-sequential passes. Specialists research and advise only. - Synthesize the evidence and produce a complete spec: title, goal, background, user stories, requirements, non-goals, UI/UX notes, data and API changes, edge cases, test plan, planning path and consultations, dependency-aware implementation tasks, review checklist, and open questions.
- For every implementation task include: ID, owner role, requirement IDs,
dependencies, ownership area, acceptance criteria, required tests,
parallelizable, and integration point/order. - Save it to
.agent/specs/<kebab-case-name>.md. - Present a concise plain-language decision summary using
/sum-spec's output contract. Stop and request approval explicitly. Do not start implementation workers.
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 · 108 lines · 30 tokens per session scan A 998790ffc169
spec is a command published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 992 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.