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/privacygit 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.00340 |
| Opus 5 | $0.00000 | $0.00170 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
privacy 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.
What it actually says
Scope
- [DECISION] This pillar captures privacy boundaries for Godpowers project-local events, adoption metrics, connectors, and exported telemetry.
Context
- [DECISION] Godpowers stores workflow state and evidence locally under
.godpowers/unless a user explicitly configures an external connector or telemetry export. - [DECISION] OTel export and connector actions are explicit capabilities rather than silent data collection.
Decisions
- [DECISION] Local evidence should record operational facts without copying secrets, credentials, or unnecessary personal content.
Rules
- [DECISION] Do not place API tokens, session values, raw credentials, or unnecessary personal data in state, events, logs, checkpoints, or sync-back files.
- [DECISION] External export requires explicit configuration and must remain visible in closeout evidence.
Workflows
- [DECISION] Before adding a new external data path, inventory collected fields, purpose, destination, retention behavior, deletion path, and user control.
Watchouts
- [HYPOTHESIS] User-authored artifact excerpts can contain personal data even when the runtime itself does not collect identity fields.
Touchpoints
- [DECISION] Privacy concerns touch
lib/events.js,lib/otel-exporter.js, connector configuration, logs, checkpoints, and source-system sync-back.
Gaps
(none)
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 · 44 lines · 0 tokens per session scan A 4bff2e74feb1
privacy 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 340 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-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-juror
L4 terminal leaf - G7 SIGN-OFF. One independent sign-off panel seat that saw none of the intermediate work. Binary PASS/FAIL on opened evidence; default-FAIL. A FAIL naming a P0/P1 blocker is NOT arbitrable into PASS.
ap-re-anchor
L4 terminal leaf - RE-ANCHOR. Confirms mission and roadmap frontier alignment after resume or compaction using the three-file governance state.
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.