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 skills/regenrek/codex-proofloop/proofloop-herdr-sol-lunanpx skills add regenrek/codex-proofloop --skill proofloop-herdr-sol-lunagit clone --depth 1 https://github.com/regenrek/codex-proofloopWrote 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/skills/regenrek/codex-proofloop/proofloop-herdr-sol-luna)<a href="https://agentmods.dev/skills/regenrek/codex-proofloop/proofloop-herdr-sol-luna"><img src="https://agentmods.dev/badge/skills/regenrek/codex-proofloop/proofloop-herdr-sol-luna.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.00092 | $0.01092 |
| Opus 5 | $0.00046 | $0.00546 |
| Sonnet 5 | $0.00018 | $0.00218 |
| Haiku 4.5 | $0.00009 | $0.00109 |
Grade A, and why
proofloop-herdr-sol-luna 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 3d 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.
Proofloop Herdr: Sol and Luna
Keep Sol responsible for the task, architecture, sole-writer implementation, integration, and final decision. Add another agent only when its distinct role materially improves the run.
Start from project policy
-
Discover the repository root with its version-control or project tooling; otherwise use the explicit working directory.
-
Read the applicable
AGENTS.mdfiles and locate the project profile they name. If none exists, adapt assets/project-profile.template.json and the AGENTS.md template inside the project before orchestrating. -
Create one run contract from assets/run-contract.template.json. Keep allowed paths project-relative and choose one literal validation command.
-
Validate both documents:
python3 scripts/validate_config.py path/to/project-profile.json path/to/run-contract.json
Stop if policy, scope, ownership, or the source task is ambiguous. Never inspect credential contents or copy credentials into prompts, logs, contracts, or evidence.
Select the smallest useful topology
- Use Sol only for ordinary implementation and deterministic validation.
- Add one Luna Max silent sentinel only when the run contract explicitly selects it for a
long-running Sol implementation.
luna_mode: nullcreates no Luna pane or process. Start it only with scripts/silent_sentinel.py; the script refuses an unselected mode and exits at settlement, owner loss, mandatory stop, or its deadline. - Add one fresh Luna Max bounded verifier only when project policy selects it and independent verification is worth a separate session.
- Add one fresh Luna Max interactive operator only for sustained UI or manual interaction that cannot be represented by the validation command. Do not overlap writers. Luna never edits product source, tests, task state, or documentation. Human owners decide subjective or manual acceptance. Sol resolves all findings and makes the final decision.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 239 B
- assets/AGENTS.md.template.md 3.0 KB
- assets/project-profile.template.json 2.2 KB
- assets/run-contract.template.json 2.1 KB
- assets/test-admission.template.json 1.1 KB
- references/orchestration.md 9.7 KB
- references/testing.md 4.9 KB
- scripts/silent_sentinel.py 21 KB runs code
- scripts/test_distillation_gate.py 19 KB runs code
- scripts/validate_config.py 26 KB runs code
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.
- 3d ago First seen · 88 lines · 92 tokens per session scan A 80f2d23876cd
proofloop-herdr-sol-luna is a skill published in the GitHub repository regenrek/codex-proofloop (38 stars, last pushed 22d ago), licensed MIT. It adds 92 tokens to every session and 1,092 once invoked, about $0.0005 per session on Opus 5. 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…