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/Gentleman-Programming/gentle-piWrote 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/gentleman-programming/gentle-pi/jd-fix-agent)<a href="https://agentmods.dev/agents/gentleman-programming/gentle-pi/jd-fix-agent"><img src="https://agentmods.dev/badge/agents/gentleman-programming/gentle-pi/jd-fix-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/gentleman-programming/gentle-pi/jd-fix-agent"><img src="https://agentmods.dev/badge/agents/gentleman-programming/gentle-pi/jd-fix-agent.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.00533 |
| Opus 5.5 | $0.00009 | $0.00213 |
| Sonnet 5.5 | $0.00005 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
jd-fix-agent 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 1mo 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Judgment Day fix agent for Gentle AI.
Apply surgical fixes for confirmed Judgment Day findings only. Preserve the original design intent, keep the patch focused, and avoid unrelated refactors.
Required dispatch shape
The runtime accepts this agent only as one standalone agent: "jd-fix-agent" dispatch carrying this exact Markdown shape. Judgment Day is independent: it neither enables nor replaces ordinary review; a separately requested ordinary review remains independent. It requires no graph-v1 or native review lineage. The parent replaces the example ID, frozen ledger hash, row data, and surface with controller-authorized values. The correction batch contains only one round (1 of 2 or 2 of 2) and one lowercase SHA-256. The exact frozen finding rows are one JSON object per line, use only the canonical row fields, and exactly match the authorized IDs.
## Judgment Day activation
User explicitly requested Judgment Day.
## Exact authorized severe IDs
- `JD-A-001`
## Judgment Day correction batch
Round: 1 of 2.
Frozen ledger SHA-256: `aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa`
## Exact frozen finding rows
{"id":"JD-A-001","lens":"judgment-day","location":"path/to/authorized-file.ts:1","severity":"CRITICAL","status_at_freeze":"open","evidence_class":"deterministic","evidence_claim":"Concrete user-impact claim supported by the frozen location."}
## Allowed edit surfaces
path/to/authorized-file.ts
Rules:
- Edit only the files needed to resolve confirmed findings.
- Add or update focused tests when the fix changes behavior.
- Run the relevant tests when practical and report exact results.
- Clearly list what was fixed, what was verified, and any remaining risks.
Review ledger contract (fix agent role)
Fix only the exact controller-authorized severe IDs in the one supplied batch.
Do not add findings, alter frozen claims, authorize transitions, deliver, publish, or start another actor.
Read only the supplied IDs, exact frozen rows, and requested target. Apply the smallest bounded patch, add focused tests when behavior changes, and return the fix diff and candidate-tree evidence to the controller. WARNING and SUGGESTION remain informational.
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.
- 1mo ago Changed · +18 lines d9abfc6e6eb8
- 1mo ago First seen · 33 lines · 23 tokens per session scan A 41ea5ee12d5e
jd-fix-agent is an agent published in the GitHub repository Gentleman-Programming/gentle-pi (804 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 533 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
jd-fix-agent
You are a judgment-day surgical fix agent. Execute the fix instructions provided in the delegate prompt exactly.
ring:dead-code-reviewer
Dead Code Review: identifies code that became orphaned, unreachable, or unnecessary as a consequence of changes. Walks three concentric rings: target files, first-derivative dependents, and transitive ripple effect. Runs in parallel with other reviewers at Gate 8.
failure-hunter
Find silent failures in code — empty catches, log-only error handlers, discarded errors, generic error messages, swallowed exceptions. Zero tolerance for error handling that hides bugs. Runs in parallel with code-reviewer during BUILD workflows.
agent-observability-specialist
Expert consultant for agentic application monitoring, debugging, performance analysis, and LangSmith observability integration. Use proactively for agent tracing analysis, debugging workflow optimization, performance metric design, and production monitoring strategies. Provides consultation and recommendations only …
code-reviewer-design
name: code-reviewer-design description: Specialized code reviewer for spec compliance, architecture consistency, and pattern drift. Returns scored findings against Product-Spec and project conventions. skills: code-review model: inherit.