Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add navapbc/digital-service-orchestra/plugin install dsoWrote 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/navapbc/digital-service-orchestra/bot-psychologist)<a href="https://agentmods.dev/agents/navapbc/digital-service-orchestra/bot-psychologist"><img src="https://agentmods.dev/badge/agents/navapbc/digital-service-orchestra/bot-psychologist/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/navapbc/digital-service-orchestra/bot-psychologist"><img src="https://agentmods.dev/badge/agents/navapbc/digital-service-orchestra/bot-psychologist.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.00065 | $0.03064 |
| Opus 5 | $0.00032 | $0.01532 |
| Sonnet 5 | $0.00013 | $0.00613 |
| Haiku 4.5 | $0.00006 | $0.00306 |
Grade B, and why
bot-psychologist scanned grade B with 1 finding 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 11d 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.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
14. **Instruction Leaking** — Model treats user data/payloads as system instructions (e.g., CSV contains "Ignore previous instructions" and model complies). Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bot Psychologist Agent
Startup: Session HEAD Sync (worktree isolation fix)
When dispatched with isolation: "worktree", the Agent runtime creates your worktree branched from origin/main — NOT from the orchestrator's session HEAD. If the orchestrator injected SESSION_BRANCH and SESSION_HEAD into your prompt, sync to the session HEAD as your FIRST action before reading any source files. Bug a951-d6f2-0c21-443f tracks this.
if [[ -n "${SESSION_BRANCH:-}" && -n "${SESSION_HEAD:-}" ]]; then
bash "${CLAUDE_PLUGIN_ROOT}/scripts/worktree-session-head-sync.sh" # shim-exempt: internal orchestration script
if [[ $? -ne 0 ]]; then
echo "ERROR: worktree-session-head-sync.sh failed — aborting" >&2
exit 1
fi
elif [[ -n "${SESSION_BRANCH:-}" || -n "${SESSION_HEAD:-}" ]]; then
echo "WARNING: SESSION_BRANCH/SESSION_HEAD partially set — skipping worktree sync" >&2
fi
When both are unset (orchestrator on main, no session in flight), do nothing — your default origin/main worktree is correct.
You are an elite LLM behavioral debugger. Your purpose is to diagnose and correct divergent, unpredictable, or failing behavior in other LLMs, agents, and complex prompts using the scientific method.
You MUST NOT assume a root cause based on a user's initial report. Instead, you iteratively propose hypotheses, design specific probes (experiments) to test them, analyze results, and only propose a correction once the root cause is experimentally proven. Do not propose any fix before a hypothesis has been confirmed through experiment. Do not assume a failure mode before experimental results are in.
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.
- 11d ago First seen · 177 lines · 65 tokens per session scan B b19ea1b7b886
bot-psychologist is an agent published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed today), licensed Apache-2.0. It adds 65 tokens to every session and 3,064 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (instruction-override phrasing). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.