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/JoakimCarlsson/bastionWrote 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/joakimcarlsson/bastion/subagents)<a href="https://agentmods.dev/rules/joakimcarlsson/bastion/subagents"><img src="https://agentmods.dev/badge/rules/joakimcarlsson/bastion/subagents/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/joakimcarlsson/bastion/subagents"><img src="https://agentmods.dev/badge/rules/joakimcarlsson/bastion/subagents.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.00661 | $0.00661 |
| Opus 5.5 | $0.00264 | $0.00264 |
| Sonnet 5.5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
subagents 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 1mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagents and workflow
Tools
- GitHub:
ghonly (issues, labels, milestones, PRs) — not the web UI for bulk work - Git: local repo operations only
- PowerShell: use
--body-filefor issue/PR bodies; no bash heredocs
Agents (invoke explicitly)
| Agent | Slash | Role |
|---|---|---|
| issue-creator | /issue-creator |
Issues, labels, milestones — standalone, stops when done |
| planner | /planner |
Pick issue, gh issue develop → linked task/<N>-<slug> branch, plan (no source edits) |
| coder | /coder |
Implement from HANDOFF:PLAN or HANDOFF:FIX |
| smoke-tester | /smoke-tester |
Build, test, HTTP smoke checks |
| reviewer | /reviewer |
Final review; blocking issues → HANDOFF:FIX → coder; on approval commits, pushes, opens PR |
Delivery pipeline: /planner → /coder → /smoke-tester → /reviewer
Auto-handoff (required): When a pipeline agent finishes with a HANDOFF block and next_agent set, immediately delegate to that agent via the Task tool. Pass the full HANDOFF block unchanged in the Task prompt. Do not stop and ask the user to run the next slash command or paste the handoff manually.
| HANDOFF | Next agent |
|---|---|
HANDOFF:PLAN |
coder |
HANDOFF:IMPLEMENTATION |
smoke-tester |
HANDOFF:VERIFIED |
reviewer |
HANDOFF:FIX |
coder (from smoke-tester or reviewer) |
issue-creator is standalone — no auto-chain after it.
HANDOFF blocks
Copy unchanged between agents:
HANDOFF:PLAN— planner → coderHANDOFF:IMPLEMENTATION— coder → smoke-testerHANDOFF:VERIFIED— smoke-tester → reviewerHANDOFF:FIX— smoke-tester or reviewer → coder
Small tasks
For typos or one-file fixes, skip planner and smoke-tester; use /coder then auto-handoff to reviewer with HANDOFF:VERIFIED or a minimal verification summary if smoke-tester was skipped.
Verification commands
Before smoke-testing, read .cursor/verify-commands.md. Update that file when the project stack is chosen.
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.
- 1mo ago First seen · 60 lines · 661 tokens per session scan A 8fcc40498884
subagents is a cursor rule published in the GitHub repository JoakimCarlsson/bastion (2 stars, last pushed 4mo ago), licensed MIT. It adds 661 tokens to every session, about $0.0026 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
nauro-ship-task
Run the full planner -> executor -> reviewer -> tech-lead -> direct-user-confirm -> push chain through Cursor's native project workflow agents. Requires the four bundled .cursor/agents/nauro-.md definitions and fails closed without native dispatch.
conventional-commits
Conventional Commits mapped to SemVer; use this repo's types and scopes for commit and PR titles.
handoff
Export a Waybill Bundle by default, or import one when explicitly requested.
git-linear-automation
A set of rules for automating Git work and linking commits or pull requests with Linear, a project-management issue tracker.
git-conventions
Git workflow and commit conventions for AI-assisted development.
roslyn-mcp-version-bump
Auto-bump Version after successful MCP self-build and reload.