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 skills add Oriolshhh/runware-image-mcp --skill spec-engineeringgit 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/skills/oriolshhh/runware-image-mcp/spec-engineering)<a href="https://agentmods.dev/skills/oriolshhh/runware-image-mcp/spec-engineering"><img src="https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/spec-engineering/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/skills/oriolshhh/runware-image-mcp/spec-engineering"><img src="https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/spec-engineering.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.00011 | $0.00615 |
| Opus 5 | $0.00005 | $0.00308 |
| Sonnet 5 | $0.00002 | $0.00123 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
spec-engineering 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 8d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Engineering
Purpose
Convert a request into a precise, testable specification that a reviewer can approve and an implementer can follow without guessing.
When to use it
- Any non-trivial change, new feature, or behavior change.
- When requirements are ambiguous or stakeholders disagree.
Instructions
- Read fresh repository context and relevant source before asking questions.
- Ask one batch of at most three decision-changing questions (five only when unavoidable); state safe defaults for non-blocking ambiguity.
- Choose
direct-spec,specialist-assisted-spec, orfull-council-specfrom complexity, reversibility, cross-cutting scope, security, and product risk. - For specialist-assisted planning, select only relevant reviewers and gather
separate evidence-backed reports, parallelizing only with native isolated
agents. Use
/councilfor the full-council path. - Capture background, user stories, explicit non-goals, assumptions, and any meaningful specialist disagreement.
- Write numbered, testable requirements and map tests to each requirement.
- Describe data/API changes, UI/UX states, compatibility, rollout, and edge cases.
- Break work into dependency-aware tasks. Each task names its owner role, requirement IDs, dependencies, ownership area, acceptance criteria, tests, parallelizability, and integration point.
- Save to
.agent/specs/<kebab-case-name>.mdand request approval. - Include the
/specfrontmatter contract and keep status/revision metadata synchronized when the document changes.
Output format
A single Markdown spec with: title, goal, background, user stories, requirements, non-goals, UI/UX notes, data and API changes, edge cases, test plan, planning path and consultations, implementation tasks, review checklist, open questions.
Anti-patterns
- Vague requirements that cannot be verified.
- Silent assumptions instead of explicit open questions.
- Asking the user for information available in repository context.
- Invoking every specialist regardless of relevance.
- Calling simulated role passes independent subagents.
- Marking tasks parallelizable despite shared files or unresolved dependencies.
- Starting implementation before approval.
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.
- 8d ago First seen · 61 lines · 11 tokens per session scan A ed48733554f0
spec-engineering is a skill published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 615 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…