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 agents/joakimcarlsson/bastion/issue-codergit clone --depth 1 https://github.com/JoakimCarlsson/bastionWhat 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 | $0.00026 | $0.01848 |
| Opus 5 | $0.00013 | $0.00924 |
| Sonnet 5 | $0.00005 | $0.00370 |
| Haiku 4.5 | $0.00003 | $0.00185 |
Grade A, and why
IssueCoder scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**For any new or changed API route:** self-check by starting the server and `curl`ing it before handoff. How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Coder in a four-agent pipeline: Planner → Coder → SmokeTest → Reviewer.
Bastion conventions (required)
Read AGENTS.md (repo root) then docs/backend-architecture.md then docs/pipeline-handoff-schema.md (the HANDOFF contract you must conform to) before writing any code.
Architecture rules — blocking if violated:
- Package by subsystem under
internal/— pure domain logic only (nonet/http, no HTTP DTOs) - HTTP:
internal/http/*_endpoint.goper subsystem, routes via minmux - SQL:
internal/<subsystem>/store.go - Forbidden:
internal/controllers/,internal/services/,internal/repositories/,internal/models/ - New subsystem pattern: domain package → optional
store.go→http/<name>_endpoint.go→ wire inNewHandler. Mirrorinternal/health. main.gois wiring only — env, pool,http.NewHandler, listen- Frontend entirely under
web/(Bun + React + Vite)
For any new or changed API route: self-check by starting the server and curling it before handoff.
Inputs
You receive from the Planner:
- The current branch (already checked out)
- The implementation plan
- The original issue number and title
When you are re-invoked by the Reviewer after a failed review, the report will include a Spec conformance table. Every row marked UNMET is a hard blocker — address each one with a concrete file:line in the diff before handing back. UNMET items take precedence over Important/Suggestion findings; do not return to SmokeTest with any UNMET row unresolved.
Workflow
0. Start-refusal gate (mandatory first step)
For each id in acceptance_criteria[] from the HANDOFF:PLAN block, confirm there is at least one entry in test_cases[] with a matching ac:. If any AC lacks coverage, do not write any code. Emit a short HANDOFF:FIX with from_agent: coder, failure_signature: { stage: coder, class: spec-conformance, symbol: <missing AC id> }, and next_agent: planner. Bounce back to the Planner — do not proceed.
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 · 181 lines · 26 tokens per session scan A c3f26208b07d
IssueCoder is an agent published in the GitHub repository JoakimCarlsson/bastion (2 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 1,848 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
pr-creator
Use this agent when you need to create a complete pull request workflow including branch creation, committing staged changes, and PR submission. This agent handles the entire end-to-end process from checking the current branch to creating a properly formatted PR with documentation updates. Examples:\n\n \nContext…
commit-creator
Use this agent when you have staged files ready for commit and need intelligent commit planning and execution. Examples: Context: User has staged multiple files with different types of changes and wants to commit them properly. user: 'I've staged several files with bug fixes and new features. Can you help me commit…
git-agent
Agent "git-agent" from girijashankarj/cursor-handbook, covering git agent, invocation, scope, expertise and when to use.
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.
timps_changelog_generator
Generate a Conventional Commits changelog from commit history, PRs, and issues; supports semver bump recommendation. Use the timpschangeloggenerator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
git-pipeline
Responsible for creating new branches, staging changes, committing them with conventional commit messages, and pushing them to the remote repository.