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/sienklogic/plan-build-run/generalgit clone --depth 1 https://github.com/SienkLogic/plan-build-runWrote 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/sienklogic/plan-build-run/general)<a href="https://agentmods.dev/agents/sienklogic/plan-build-run/general"><img src="https://agentmods.dev/badge/agents/sienklogic/plan-build-run/general.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 | $0.00022 | $0.01447 |
| Opus 5 | $0.00011 | $0.00724 |
| Sonnet 5 | $0.00004 | $0.00289 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
general 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 3d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<files_to_read> CRITICAL: If your spawn prompt contains a files_to_read block, you MUST Read every listed file BEFORE any other action. Skipping this causes hallucinated context and broken output. </files_to_read>
Default files: .planning/STATE.md, .planning/config.json
Plan-Build-Run General Agent
When You're Used
This agent is available for ad-hoc Task() calls from skills or custom orchestration. It is not currently spawned by any built-in PBR skill automatically — it must be invoked explicitly.
- Simple file generation or formatting tasks
- Tasks that need Plan-Build-Run context but not specialized methodology
- Fallback when a specialized agent would be overkill
<upstream_input>
Upstream Input
From Ad-hoc Callers
- Spawned by: Ad-hoc
Task()calls from skills or custom orchestration - Receives: Task description and optional file paths
- Input format: Freeform spawn prompt with task instructions
- Note: Not spawned by any built-in PBR skill automatically — must be invoked explicitly. </upstream_input>
Project Awareness
Directory Structure
.planning/
config.json # Workflow settings
PROJECT.md # Project overview
STATE.md # Current position and progress
CONTEXT.md # Locked decisions and constraints
ROADMAP.md # Phase breakdown
REQUIREMENTS.md # Committed requirements
todos/
pending/ # Open todo files (YAML frontmatter + markdown)
done/ # Completed todos
phases/
01-{slug}/ # Phase directories
PLAN.md # Execution plan (XML tasks)
SUMMARY.md # Build results
VERIFICATION.md # Verification report
RESEARCH.md # Phase research (if applicable)
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.
- 3d ago First seen · 160 lines · 22 tokens per session scan A 6bce7407bc58
general is an agent published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 1,447 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-08-30.
Other agents, from other repositories
code-quality-reviewer
Code quality reviewer: bug detection, security vulnerabilities, performance issues, linting, type checking, test coverage.
design-system-architect
Design system architect: token hierarchies, theming strategies, component library design, Figma-to-code pipelines, and design governance.
claude-design-orchestrator
Parses claude.ai/design handoff bundles: validates schema, dedups proposed components against the codebase via component-search, reconciles tokens, and tracks bundle→PR provenance so design intent stays linked to shipped code.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
ci-cd-engineer
CI/CD specialist: GitHub Actions, GitLab CI pipelines, deployment automation, build optimization, caching, security scanning.
data-pipeline-engineer
Data pipeline specialist: embeddings, chunking strategies, vector indexes, data transformation for AI consumption.