context

A project-context guide that records durable facts, decisions, rules, and workflows for an AI-powered development system. It explains how project guidance and workflow state are stored for coding agents.

In plain words
What is it for?
Use it to understand the project's purpose, audience, slash commands, context files, workflow state, and documented product decisions.
Why use it?
It gives agents consistent background about the product and its operating model instead of making assumptions from individual files or requests.

Agent

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/context
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 1,956 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01956
Opus 5 $0.00000 $0.00978
Sonnet 5 $0.00000 $0.00391
Haiku 4.5 $0.00000 $0.00196

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

Security

Grade A, and why

context 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/context.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Scope

  • [DECISION] This pillar captures durable product context for the Godpowers repository.

Context

  • [DECISION] Godpowers is an AI-powered development system delivered as slash commands and specialist agents inside AI coding tools.
  • [DECISION] The package name is godpowers, and the current repository version is 6.3.0.
  • [DECISION] The primary audience is solo founders and small engineering teams using AI coding tools who need accountable production workflow discipline without enterprise process.
  • [DECISION] The product promise is one slash-command arc from idea to hardened, observable, launch-ready software with traceable artifacts on disk.
  • [DECISION] Godpowers uses a pure-skill model where npx godpowers installs runtime files and in-tool slash commands perform work.
  • [DECISION] The native context layer is Pillars: root AGENTS.md plus routed agents/*.md files.
  • [DECISION] Workflow state lives in .godpowers/ and is authoritative for Godpowers command resumes.

Decisions

  • [DECISION] Godpowers 6.3.0 adds product-form verification, feedback-loop debugging, deeper program design, cited why evidence, durable decision traces, and one canonical invocation policy per core route.
  • [DECISION] The optional @godpowers/operations-pack provides issue triage and a human-only setup wizard without adding a core command or root runtime dependency.
  • [DECISION] Godpowers 6.3.0 and @godpowers/operations-pack 0.1.0 are published and verified from merged main commit c45d0473ad946fcd7c02a5706b02f51a40ed0d25.
  • [DECISION] Existing /god-review and /god-build Stage 2 review uses references/building/BLAST-RADIUS.md to grade exactly one load-bearing safety fact against a five-level evidence ladder and 10 boundary classes.
  • [DECISION] The blast-radius behavior adds no command, route, recipe, workflow, specialist type, production dependency, evidence store, state writer, or execution authority.
  • [DECISION] The npm package includes references/building/BLAST-RADIUS.md, and installation copies the reference into godpowers-references/ and the installed runtime bundle through existing data-directory behavior.

Read the full file on GitHub · 100 lines

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.

  1. yesterday First seen · 100 lines · 0 tokens per session scan A 2dbdcaed7dff

Subscribe to this mod's changes

context 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,956 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.