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/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/sum-spec)<a href="https://agentmods.dev/commands/oriolshhh/runware-image-mcp/sum-spec"><img src="https://agentmods.dev/badge/commands/oriolshhh/runware-image-mcp/sum-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.00029 | $0.00649 |
| Opus 5 | $0.00015 | $0.00324 |
| Sonnet 5 | $0.00006 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
sum-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 7d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sum-spec — Explain a specification clearly
Purpose
Turn a complete specification into a short, decision-ready explanation without changing its meaning, editing it, or approving it.
Invocation
/sum-spec [spec name or path]
Accepted input
An explicit .agent/specs/*.md path, a spec name, or the current spec from the
conversation.
Prerequisites
An existing specification. This command does not create or repair one.
Procedure
- Resolve the requested spec. Prefer an explicit path or name, then the spec
identified in the conversation. If neither is available, use the only spec
with
status: awaiting-approval. If multiple candidates remain, list them briefly and ask the user to choose; never guess. - Read the entire spec, including frontmatter, requirements, non-goals, tasks, test plan, risks, migrations, rollout, and open questions. Do not broadly scan the repository unless the user asks you to verify the spec.
- Translate implementation language into plain language while preserving concrete behavior, scope boundaries, dependencies, and uncertainty. Expand unfamiliar acronyms once. Do not invent missing details.
- Produce the output below. Keep it under 500 words by default; use up to 800 only when shortening further would hide a material risk or decision.
- End with exactly what approval authorizes and any question that must be answered first. Do not change spec status or begin implementation.
Expected output
Use these headings:
- In one sentence — the intended outcome.
- What will change — three to seven concrete user or system behaviors.
- How it will be built — affected areas and implementation sequence, without line-by-line task repetition.
- How we will know it works — the important tests and validation gates.
- Risks and boundaries — material risks, compatibility or rollout work, non-goals, and assumptions.
- Decisions needed — unresolved questions, or
None. - Approval means — the precise scope the agent may implement next.
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.
- 7d ago First seen · 71 lines · 29 tokens per session scan A 5132ba47f27e
sum-spec is a command published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 649 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-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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.