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/Dankosik/go-service-template-restWrote 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/dankosik/go-service-template-rest/agent-harness)<a href="https://agentmods.dev/rules/dankosik/go-service-template-rest/agent-harness"><img src="https://agentmods.dev/badge/rules/dankosik/go-service-template-rest/agent-harness/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/rules/dankosik/go-service-template-rest/agent-harness"><img src="https://agentmods.dev/badge/rules/dankosik/go-service-template-rest/agent-harness.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.00078 | $0.00078 |
| Opus 5.5 | $0.00031 | $0.00031 |
| Sonnet 5.5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
agent-harness 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 2mo 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.
What it actually says
This is a Cursor session. When a native control is needed, load Agent Harness and only its Cursor adapter. Sibling bootstrap files select other harnesses; do not follow their adapter choice.
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.
- 2mo ago First seen · 10 lines · 78 tokens per session scan A 79d8e2ec7258
agent-harness is a cursor rule published in the GitHub repository Dankosik/go-service-template-rest (8 stars, last pushed today), licensed MIT. It adds 78 tokens to every session, about $0.0003 per session on Opus 5.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 cursor rules, from other repositories
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
miro-best-practices
MCP server for controlling Miro whiteboards with AI assistants.
agentic-loop
Vault agentic develop→validate loop — follow on every coding task.
architecture
Core file-system logic stays UI-agnostic; platform-specific quirks stay behind an adapter per OS.
unit-tests-tdd
TDD for behavior changes; co-located tests; keep touched areas well covered.
minimal-communication
Minimal-communication response style — facts only, no validation, small phrases. Always active.