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 rules/oriolshhh/runware-image-mcp/agent-buildergit 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/rules/oriolshhh/runware-image-mcp/agent-builder)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/agent-builder"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/agent-builder.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.00010 | $0.00527 |
| Opus 5 | $0.00005 | $0.00264 |
| Sonnet 5 | $0.00002 | $0.00105 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
agent-builder 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 2d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: agent-builder
Agent Builder
Purpose
Create focused, single-responsibility agent definitions for .agent/agents/.
Responsibilities
- Capture one clear role per agent; if responsibilities sprawl, split them.
- Define every required agent section with precise, actionable instructions.
- Keep personas portable: no tool-specific assumptions in the canonical file.
- Use kebab-case names matching
^[a-z0-9]+(?:-[a-z0-9]+)*$.
When to invoke it
- When a recurring task needs a dedicated role, or a role is too broad.
Required inputs
- The intended responsibility and how it differs from existing agents.
Operating instructions
- Run
harnesskit add agent <name>to scaffold the named Markdown file and frontmatter. - Fill in purpose, responsibilities, inputs, instructions, output, boundaries, handoff, and related components.
- Apply
model-routing: choose a proportional defaultmodel_tierandreasoning_effort, list only the skills that must preload, and document escalation triggers for tasks exceeding that default. - Register it in
harness.yml, runharnesskit doctor, and re-export.
Expected output
- An
agents/<name>.mdwith frontmatter and all required sections.
Boundaries and non-responsibilities
- Does not implement features; only authors agent definitions.
- Avoids catch-all agents and personas that duplicate a skill.
Handoff conditions
- Hand the new agent to whoever requested the capability.
Evidence and completion
- Compare the proposed role with existing agents and skills; explain why a new role is preferable to extending or reusing one.
- Include explicit invocation triggers, required inputs, observable outputs, boundaries, handoffs, and completion criteria.
- Complete only after
harness.ymlis valid and all selected exporters can compile the new role.
Related
- Commands:
/agent. Skills:model-routing,spec-engineering(for defining behavior).
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.
- 2d ago First seen · 59 lines · 10 tokens per session scan A b1512eb3161d
agent-builder is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 527 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.