A project-development guide for the Godpowers repository. It records the repository's working rules, test commands, file conventions, and contributor workflow.

Use it to choose focused tests, run the full checks, decide where runtime changes belong, follow repository routes, and prepare changes for handoff.

It gives coding agents project-specific instructions they cannot safely infer from source code alone, while helping protect generated files and unrelated user changes.

development — Agent by hannsxpeter

Install

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.

agentmods

npx agentmods add agents/hannsxpeter/godpowers/development

Clone the repo

git clone --depth 1 https://github.com/hannsxpeter/godpowers

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 394 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00394
Opus 5	$0.00000	$0.00197
Sonnet 5	$0.00000	$0.00079
Haiku 4.5	$0.00000	$0.00039

Measured yesterday against content hash f42aef4369b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

development 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 yesterday.

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.

agents/development.md · 47 lines

What it actually says

Scope

[DECISION] This pillar captures the contributor inner loop for the Godpowers repository.

Context

[DECISION] Contributors use Node.js 18 or newer and npm from the repository root.
[DECISION] Source-controlled commands, specialist contracts, routes, workflows, schemas, and runtime helpers are edited in place without a compilation step.
[DECISION] Generated .godpowers/PROGRESS.mdx and tier state views derive from .godpowers/state.json and must not be edited directly.

Decisions

[DECISION] Focused tests run before npm test, while npm run release:check is reserved for complete release evidence because it includes coverage and package checks.

Rules

[DECISION] Preserve unrelated user changes in dirty worktrees.
[DECISION] Add new runtime behavior in lib/ and keep bin/install.js a thin dispatch surface.

Workflows

[DECISION] Read the applicable Pillars load set and source-controlled route before changing a command.
[DECISION] Run the smallest focused test that exercises the change.
[DECISION] Run npm test, npm run lint, and relevant package checks before handoff.

Watchouts

[HYPOTHESIS] Direct edits to generated views can appear correct locally while leaving authoritative state stale.

Touchpoints

[DECISION] Development workflow touches lib/, scripts/, skills/, specialists/, routing/, workflows/, and .godpowers/state.json.

Gaps

(none)

Changes

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.

yesterday First seen · 47 lines · 0 tokens per session scan A f42aef4369b4

Subscribe to this mod's changes

development 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 394 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.

Productivity Testing agent-orchestration ai-coding claude-code codex cursor developer-tools

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…

Spielewoy/autoprompt-skill · 93 tokens

development

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Scope

Context

Decisions

Rules

Workflows

Watchouts

Touchpoints

Gaps

What this file has done since we first saw it

Other agents, from other repositories

ap-framework-generator

ap-juror

ap-verifier

ap-re-anchor

domain

ijfw-extract-learnings