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/loop-spec-to-implementationgit 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/loop-spec-to-implementation)<a href="https://agentmods.dev/commands/oriolshhh/runware-image-mcp/loop-spec-to-implementation"><img src="https://agentmods.dev/badge/commands/oriolshhh/runware-image-mcp/loop-spec-to-implementation.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.00000 | $0.00372 |
| Opus 5 | $0.00000 | $0.00186 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
loop-spec-to-implementation 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 yesterday.
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
80% identical to loop-context-compression — 35 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.
What it actually says
/loop-spec-to-implementation — Adaptive spec planning, approve, implement, verify gates.
Follow this ordered workflow. Respect every human-approval gate and stop when instructed.
name: spec-to-implementation
description: Turn a request into an approved spec, then implement it with passing gates.
max_iterations: 3
steps:
- name: spec
command: /spec
instruction: >-
Inspect context, ask one minimal blocker batch, choose direct,
specialist-assisted, or full-council planning, gather selected planning
reviews when useful, and save a dependency-aware spec under .agent/specs/.
- name: approve
instruction: Wait for explicit human approval of the spec before coding.
gate: human-approval
- name: implement
command: /implement
instruction: >-
Implement the approved spec with the smallest reasonable diff. Route
user-facing rendered UI tasks to frontend-implementer with design-system,
UI-state, responsive, accessibility, and frontend guideline skills;
require visual-qa-tester browser validation afterward. Apply
code-quality-guidelines for all implementation and architecture/backend/
frontend guideline skills by surface. Load motion only when changed and
return unresolved material direction to frontend-design before coding.
- name: verify
instruction: Run the configured gates and make them pass.
gate: gates/default.yml
Apply
context-discoverybefore broad scanning: use a supplied context capsule first; otherwise check context frontmatter freshness, read.agent/context/routing.md, load only relevant summaries, and verify critical claims against source.
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.
- yesterday First seen · 37 lines · 0 tokens per session scan A 50d759539a45
loop-spec-to-implementation is a command published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 372 tokens. A static security scan graded it A with 0 findings. It is 80% identical to loop-context-compression, differing in 35 lines, and is treated as a copy.
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.
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.