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/hannsxpeter/godpowers/archgit clone --depth 1 https://github.com/hannsxpeter/godpowersWhat 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.00000 | $0.01479 |
| Opus 5 | $0.00000 | $0.00740 |
| Sonnet 5 | $0.00000 | $0.00296 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
arch 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 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.
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope
- [DECISION] This pillar captures architectural context for Godpowers.
Context
- [DECISION] Runtime architecture is implemented by source-controlled skills, routes, workflows, specialist contracts, schemas, and dependency-free Node.js helpers.
Decisions
- [DECISION] Godpowers uses a pure-skill runtime where slash-command skills spawn specialist agents inside the host AI coding tool.
- [DECISION] The CLI surface stays narrow: installer and uninstall flows, read-only status and next-route helpers, automation status and setup planning, dogfood fixtures, and extension scaffolding.
- [DECISION] Routing decisions are stored in
routing/*.yaml. - [DECISION] Workflow plans are stored in
workflows/*.yamland planned bylib/workflow-runner.js. - [DECISION] Workflow plans can expose visible local helpers such as
repo-doc-sync,repo-surface-sync,host-capabilities,source-sync-back, andcheckpoint-sync. - [DECISION]
lib/state-lock.jsprovides cooperative advisory locking through.godpowers/state.json. - [DECISION] Existing
.godpowersprojects refresh runtime feature awareness throughlib/feature-awareness.js. - [DECISION]
ARCHITECTURE.mdowns the architecture audit playbook for disconnected commands, actions, and workflows. - [DECISION]
ARCHITECTURE-MAP.mdrenders the same audit as a graph from skills to routes, agents, workflows, recipes, docs, and package checks. - [DECISION]
ARCHITECTURE-MAP.mdkeeps a complete core command supplement so all 124 shipped skills appear in the human-readable map. - [DECISION] Workflow plans use canonical helper IDs such as
source-sync-backandpillars-sync-plan, while/god-syncoutput may show the shorter aliasessource-syncandpillars-sync. - [DECISION] Godaudits 2.x interoperability reads
.godaudits/AUDIT.jsonas canonical machine state, imports explicit check outcomes, evidence metadata, compliance, accepted risks, open questions, score caps, coverage, findings, and typed GA tasks, and uses generated or legacy AUDIT.mdx only as a fallback. - [DECISION] Godplans 1.1 interoperability treats
.godplans/PLAN.mdxplus the pinned executable.godplans/validate-plan.shas one contract, mirrors structural validation without executing repository shell during import, blocks GP dispatch outsideapprovedorexecuting, and requires the official validator to pass immediately before work. - [DECISION]
lib/prose-lint.jsstays inside the existing artifact-quality boundary as a dependency-free inert-text scanner with no I/O, bounded sanitized excerpts, and warning-only U-12 integration throughlib/have-nots-validator.js. - [DECISION]
references/building/BLAST-RADIUS.mdis the single Stage 2 safety-case protocol consumed by/god-review,/god-build,god-executor,god-quality-reviewer, and the orchestrator runbook. - [DECISION]
god-executorproposes a candidate safety fact and focused proof but does not grade its own work;god-quality-reviewerindependently verifies or replaces the candidate and owns the Stage 2 verdict. - [DECISION]
lib/impact.jsremains a static candidate generator with unproven maximum-level-2 metadata, while the existing evidence ledger remains the executed-proof authority. - [DECISION]
lib/evidence.resolveReviewEvidenceadds a read-only sanitized projection over unchanged verification records and additive record-ID and record-digest gate-event bindings. - [DECISION] Bounded changes receive 1 Stage 2 safety case; changes crossing at least 3 boundary classes or at least 2 high-impact classes receive at least 2 independent fresh-context safety cases before reconciliation.
- [DECISION] The blast-radius design adds no command, route, recipe, workflow, specialist type, production dependency, evidence store, or state writer.
- [DECISION]
lib/verification-profile.js,lib/debug-feedback-loop.js,lib/program-design.js,lib/why-evidence.js,lib/events.js, andlib/invocation-policy.jsadd bounded evidence and authority contracts inside existing runtime boundaries. - [DECISION] Canonical route filenames own command identity, and route loading rejects duplicate, spoofed, or noncanonical YAML before invocation policy can be consumed.
- [DECISION]
@godpowers/operations-packremains a lazy extension with no core route and no automatic external mutation authority. - [DECISION] The current executable audit status is fresh for repo surface, route quality, recipe coverage, and workflow planning.
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 · 88 lines · 0 tokens per session scan A 7d9e34284b41
arch is an agent published in the GitHub repository hannsxpeter/godpowers (5 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,479 tokens. 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 agents, from other repositories
ap-manager
L2 optional manager - coordinates a multi-lane slice, builds compact pointer envelopes, and dispatches disjoint L3 work without executing it.
ap-framework-generator
L3 executor - FRAMEWORK GENERATE. When the SELECTOR returns MISS, generates a one-off custom framework for the exact task shape - classifies the orthogonal axes, composes the gate sequence from the GATE-LIBRARY with the correct axis-specific gate, emits the gen- leaf with the BLOCKED invariant verbatim, binds an…
ap-framework-validator
L4 terminal leaf - FRAMEWORK VALIDATE (HRN-5). A fresh, default-FAIL juror that proves a GENERATED framework is SOUND before any gate runs. Checks the HRN-5 default-FAIL checklist - every gate mapped, exactly one terminal DONE with negatives looping UP, the BLOCKED invariant verbatim, a non-empty acceptance set. PASS…
ap-scoper
L3 useful-first roadmap author or complementary scout - proves capability when needed, inspects the real repository, and contributes to one executable ROADMAP.md without spawning.
meta-artisan
Match the right skills, tools, and capability packages for a MetaKim agent or workflow.
meta-scout
Discover external tools and skills to close MetaKim capability gaps.