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/repogit clone --depth 1 https://github.com/hannsxpeter/godpowersWrote 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/hannsxpeter/godpowers/repo)<a href="https://agentmods.dev/agents/hannsxpeter/godpowers/repo"><img src="https://agentmods.dev/badge/agents/hannsxpeter/godpowers/repo.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.00000 | $0.00781 |
| Opus 5 | $0.00000 | $0.00391 |
| Sonnet 5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
repo 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 4d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope
- [DECISION] This pillar captures repository structure and command conventions for Godpowers.
Context
Layout
- [DECISION]
SKILL.mdis the main installed skill entry point. - [DECISION]
skills/contains one slash-command skill markdown file per command. - [DECISION]
agents/contains specialist agent markdown files and project Pillars files. - [DECISION]
routing/contains command routing YAML files androuting/recipes/contains fuzzy-intent recipes. - [DECISION]
workflows/contains workflow YAML definitions used bylib/workflow-runner.js. - [DECISION]
schema/contains JSON schemas for state, events, intent, routing, recipes, workflows, and extension manifests. - [DECISION]
lib/contains runtime helpers for state, routing, workflow planning, artifact linting, linkage, events, locks, checkpoints, Pillars, feature awareness, repository sync, host capabilities, dogfood, extension authoring, and suite state. - [DECISION]
scripts/contains validation and release checks. - [DECISION]
tests/contains integration fixtures and workflow smoke tests. - [DECISION]
templates/andreferences/contain artifact scaffolds and have-nots guidance. - [DECISION]
fixtures/dogfood/contains deterministic messy-repo scenarios for release and autonomy readiness.
Commands
- [DECISION] Use
npm testfor the full local suite. - [DECISION] Use
npm run test:auditfor audit, whitespace, and documentation surface checks. - [DECISION] Use
npm run test:quick-proofto verify the proof-first onboarding docs stay linked to README, release checks, runtime expectations, and the adoption canary. - [DECISION] Use
npm run pack:checkto verify npm package contents before release. - [DECISION] Use
npm run release:checkfor the complete release gate.
Decisions
(none)
Rules
- [DECISION] Do not add production dependencies unless the installer or runtime need them.
- [DECISION] Keep the public operation model slash-command based.
- [DECISION] Treat
bin/install.jsas the install and distribution surface, with only narrow operational helpers for status, next route, automation status, dogfood, and extension scaffolding.
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.
- 4d ago First seen · 79 lines · 0 tokens per session scan A 24e92de151f8
repo is an agent published in the GitHub repository hannsxpeter/godpowers (5 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 781 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-verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase. This is a single-context repo.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
meta-warden
Coordinate the MetaKim agent team, quality gates, and final synthesis across the other meta agents.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.