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.
git clone --depth 1 https://github.com/Oisinwang/get-shit-done-codexWrote 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/oisinwang/get-shit-done-codex/gsd-eval-planner)<a href="https://agentmods.dev/agents/oisinwang/get-shit-done-codex/gsd-eval-planner"><img src="https://agentmods.dev/badge/agents/oisinwang/get-shit-done-codex/gsd-eval-planner.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.1 | $0.00071 | $0.01691 |
| Opus 5 | $0.00036 | $0.00846 |
| Sonnet 5 | $0.00014 | $0.00338 |
| Haiku 4.5 | $0.00007 | $0.00169 |
Grade A, and why
gsd-eval-planner 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 7d 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.
This is a copy
97% identical to gsd-eval-planner — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<required_reading>
Read ~/.codex/get-shit-done/references/ai-evals.md before planning. This is your evaluation framework.
</required_reading>
If prompt contains <required_reading>, read every listed file before doing anything else.
<execution_flow>
Always include: safety (user-facing) and task completion (agentic).
Format each rubric as:
PASS: {specific acceptable behavior in domain language} FAIL: {specific unacceptable behavior in domain language} Measurement: Code / LLM Judge / Human
Assign measurement approach per dimension:
- Code-based: schema validation, required field presence, performance thresholds, regex checks
- LLM judge: tone, reasoning quality, safety violation detection �?requires calibration
- Human review: edge cases, LLM judge calibration, high-stakes sampling
Mark each dimension with priority: Critical / High / Medium.
If detected: use it as the tracing default.
If nothing detected, apply opinionated defaults:
| Concern | Default |
|---|---|
| Tracing / observability | Arize Phoenix �?open-source, self-hostable, framework-agnostic via OpenTelemetry |
| RAG eval metrics | RAGAS �?faithfulness, answer relevance, context precision/recall |
| Prompt regression / CI | Promptfoo �?CLI-first, no platform account required |
| LangChain/LangGraph | LangSmith �?overrides Phoenix if already in that ecosystem |
Include Phoenix setup in AI-SPEC.md:
# pip install arize-phoenix opentelemetry-sdk
import phoenix as px
from opentelemetry import trace
from opentelemetry.sdk.trace import TracerProvider
px.launch_app() # http://localhost:6006
provider = TracerProvider()
trace.set_tracer_provider(provider)
# Instrument: LlamaIndexInstrumentor().instrument() / LangChainInstrumentor().instrument()
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.
- 7d ago First seen · 155 lines · 71 tokens per session scan A c9ec713daa0b
gsd-eval-planner is an agent published in the GitHub repository Oisinwang/get-shit-done-codex (1 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 1,691 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to gsd-eval-planner, differing in 32 lines, and is treated as a copy.
Other agents, from other repositories
ijfw-integration-checker
Verify E2E flows that span multiple subagent worktrees after Phase D wiring.
ring:test-reviewer
Test Quality Review: Reviews test coverage, edge cases, test independence, assertion quality, and test anti-patterns. Runs in parallel with other reviewers at Gate 8.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
QCAuditor
QC sub-agent. Executes tests, static analysis, and security tools. Asks user for permission before installing missing dependencies.
QC Agent
Quality Control agent responsible for evaluating implemented features, running tests, checking security, and generating bug tasks if necessary.
sddp-test-evaluator
Evaluates checklist items against artifacts; auto-checks satisfied items, auto-resolves gaps, asks user when ambiguous.