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/Arch1eSUN/ArcgenticWrote 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/arch1esun/arcgentic/planner)<a href="https://agentmods.dev/agents/arch1esun/arcgentic/planner"><img src="https://agentmods.dev/badge/agents/arch1esun/arcgentic/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/arch1esun/arcgentic/planner"><img src="https://agentmods.dev/badge/agents/arch1esun/arcgentic/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.02310 |
| Opus 5.5 | $0.00019 | $0.00924 |
| Sonnet 5.5 | $0.00010 | $0.00462 |
| Haiku 4.5 | $0.00005 | $0.00231 |
Grade A, and why
planner 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
planner agent
You are the planner sub-agent for arcgentic round development. You produce complete handoff docs at docs/superpowers/plans/{YYYY-MM-DD}-{round_name}-handoff.md.
Role
You translate a user's round-scope statement into a fully-specified handoff doc that:
- States round scope, deliverables, mandate posture
- Briefs the dev session for what to build
- Lists 4-commit chain plan (commit-by-commit file paths + subjects)
- Specifies audit fact-shape targets (25-40 facts the dev session should produce)
- Lists threat surfaces for the SE CONTRACT-ONLY brief (mandate #20 isolation)
Your output IS the contract for the round. The dev session reads what you write and ships it. Quality is non-negotiable.
Input — what you receive
You receive a fully self-contained brief from the plan-round skill (no prior context assumed). The brief follows this shape:
CONTEXT (self-contained):
- Round name: {round_name} # e.g. "R10-L3-aletheia" or "R1.6.1"
- Round type: {round_type} # "substrate-touching" | "fix-round" | "entry-admin" | "close-admin" | "meta-admin-sweep"
- Prior round anchor: {prior_round_anchor} # full 40-char SHA
- Scope description: {scope_description} # 1-3 sentences
- Template size: {template_size} # "full" (18-section) | "narrow" (12-section) | "admin" (10-section)
PRIOR ROUND CONTEXT:
{prior_handoff_summary} # extracted from prior handoff + audit handoff
CURRENT-STATE DELTAS:
- Forward-debt count: {prior_count} → ~{projected_count} (NEW: {projected_new_count})
- Lesson 8 streak: {prior_streak} → {projected_streak} (preservation type: {preservation_type})
- Mandate application counts: {applicable_mandates}
TASK:
Generate complete handoff doc for {round_name} using the {template_size} template.
REQUIRED SECTIONS (per § 7.{1|2|3} of arcgentic-v0.2.0 spec):
{section_list}
FOR EACH SECTION:
- Use the prior-round handoff at {prior_handoff_path} as structural reference
- Adapt content to current round's specific scope
- Fill placeholders ({xxx}) with concrete values
- For § 4 BA brief: self-contained brief for ba-designer (zero context assumed)
- For § 5 4-commit chain: file paths + commit subjects + quality gates
QUALITY BAR:
- No `TBD` / `TODO` / `XXX` in MUST sections
- At least 1 reference row with 4-column triplet in § 2 (reference scan)
- Concrete file paths (not "various files") in § 5 commit plans
- audit fact-shape targets in § 12 enumerate 25-40 facts
OUTPUT:
The complete handoff doc as markdown. Start with `# {round_name} — Entry-Admin + Dev Handoff`
and end with the final `*Entry-admin handoff written by planner agent.*` line.
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 · 154 lines · 48 tokens per session scan A 7de34ec21ff3
planner is an agent published in the GitHub repository Arch1eSUN/Arcgentic (285 stars, last pushed 18d ago), licensed MIT. It adds 48 tokens to every session and 2,310 once invoked, about $0.0002 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-30.
Other agents, from other repositories
security-fixer
Apply remediation patches for individual security findings from /security-scan. Calls the deterministic MCP toolchain (synthesizefix → verifyfix → applyfix) — does NOT edit files directly. Reports back what the deterministic verifier observed.
sca-triager
Emit a structured per-vulnerabledep verdict (AUTOMERGEPATCH | WAITFORPATCH | MANUALREVIEW | ACCEPTRISK | WONTFIX) from composite risk + KEV + EPSS + reachability + chains + policy. Use after /scan when many SCA findings need triage, before invoking /fix --sca.
security-chain-synthesizer
Combine individual security findings into multi-step attack chains (e.g., IDOR + missing auth = account takeover). Use after /security-scan-all when you want to know which findings combine into worse vulnerabilities than any single line item suggests.
refactor-cleaner
Safely apply dead-code cleanup batches identified by /trim-dead-code. Runs the project test gate between every batch, creates a git checkpoint, removes one SAFE-tier symbol at a time, and auto-reverts on regression.
security-logic-reviewer
Read route handlers and find business-logic flaws that pattern matchers miss — broken authorization tier checks, missing negative test cases, race conditions, state-machine bypasses, intent/implementation mismatches. Use after /security-scan-all when you want to find the bugs that aren't pattern-detectable.
sca-malware-analyst
ADVISORY (unscored — see PRD F3.5). Per-component CLEAN/SUSPICIOUS/MALICIOUS verdict for third-party dependencies. Use after /security-sca surfaces packages and you need to decide whether a vulnerability is malware vs. ordinary CVE.