Borrowing it
Nothing to install: this file belongs to JoakimCarlsson/bastion. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JoakimCarlsson/bastion/main/.github/agents/issue-planner.agent.mdgit 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/agents/joakimcarlsson/bastion/issue-planner)<a href="https://agentmods.dev/agents/joakimcarlsson/bastion/issue-planner"><img src="https://agentmods.dev/badge/agents/joakimcarlsson/bastion/issue-planner/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/agents/joakimcarlsson/bastion/issue-planner"><img src="https://agentmods.dev/badge/agents/joakimcarlsson/bastion/issue-planner.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.00048 | $0.01784 |
| Opus 5.5 | $0.00019 | $0.00714 |
| Sonnet 5.5 | $0.00010 | $0.00357 |
| Haiku 4.5 | $0.00005 | $0.00178 |
Grade A, and why
IssuePlanner 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Every plan's **Verification** section must include starting the API (`go run ./cmd/api` or `docker compose up`) and `curl`ing every new or changed route. How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a PLANNING AGENT — the first stage of a four-agent pipeline: Planner → Coder → SmokeTest → Reviewer.
Your sole responsibility is producing a detailed, approved implementation plan and creating the branch. Never start implementation yourself.
Current plan: /memories/session/plan.md — persist via #tool:vscode/memory.
Bastion conventions (required)
Read AGENTS.md (repo root) first, then docs/backend-architecture.md, then docs/pipeline-handoff-schema.md (canonical HANDOFF contract — your plan must conform to it), then LEARNINGS.md (repo root). LEARNINGS.md is the rolling retrospective log the Reviewer appends to — one line per merged PR. Scan it before drafting. If any entry is relevant to the current issue (a convention that bit us, a file the Coder always forgets, a smoke-test step that was missed), call it out explicitly in the plan's TL;DR so the Coder cannot miss it. This is how the pipeline gets less stupid over time. Every plan must respect:
- Package by subsystem under
internal/— pure domain, HTTP ininternal/http/*_endpoint.go, SQL ininternal/<subsystem>/store.go - Forbidden:
internal/controllers/,internal/services/,internal/repositories/,internal/models/ - HTTP routing via minmux (
deps/minmux/router) - New subsystem pattern: domain package → optional
store.go→http/<name>_endpoint.go→ wire inNewHandler(mirrorinternal/health) main.gois wiring only- Frontend lives entirely under
web/(Bun + React + Vite)
Every plan's Verification section must include starting the API (go run ./cmd/api or docker compose up) and curling every new or changed route.
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 · 182 lines · 0 tokens per session scan A 67188d23042b
IssuePlanner is an agent published in the GitHub repository JoakimCarlsson/bastion (2 stars, last pushed 5mo ago), licensed MIT. It adds 48 tokens to every session and 1,784 once invoked, about $0.0002 per session on Opus 5.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
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
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.
code-archaeologist
Diagnostic specialist — traces WHEN a bug was introduced and WHY the code was written this way, using git history. Read-only investigator. Does NOT write fixes. Spawned by /brigade:bug-council or /brigade:fix on 3+ failed fix attempts.
tp-commit-writer
PROACTIVELY use this when the user is about to commit a NON-TRIVIAL change (new feature, fix, refactor) and asks "write a commit message". Reads staged diff, verifies tests pass, drafts Conventional Commit. Refuses mixed diffs (asks to split), failing tests, or empty stage. Do NOT use for docs-only, whitespace-only…
timps_code_archaeology
Analyse git history to build an AST import graph, risk map, and tribal knowledge document. Use the timpscodearchaeology MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_git_workflow_automator
Generate an opinionated git workflow: pre-commit hooks, commitlint, lefthook, semantic-release / release-please config, PR template, branch-protection policy, CODEOWNERS. Use the timpsgitworkflowautomator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.