Borrowing it
Nothing to install: this file belongs to gpt-cmdr/ras-commander. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gpt-cmdr/ras-commander/main/.claude/agents/notebook-anomaly-spotter.mdgit clone --depth 1 https://github.com/gpt-cmdr/ras-commanderWrote 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/gpt-cmdr/ras-commander/notebook-anomaly-spotter)<a href="https://agentmods.dev/agents/gpt-cmdr/ras-commander/notebook-anomaly-spotter"><img src="https://agentmods.dev/badge/agents/gpt-cmdr/ras-commander/notebook-anomaly-spotter/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/gpt-cmdr/ras-commander/notebook-anomaly-spotter"><img src="https://agentmods.dev/badge/agents/gpt-cmdr/ras-commander/notebook-anomaly-spotter.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.00080 | $0.00433 |
| Opus 5 | $0.00040 | $0.00217 |
| Sonnet 5 | $0.00016 | $0.00087 |
| Haiku 4.5 | $0.00008 | $0.00043 |
Grade A, and why
notebook-anomaly-spotter 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 9d 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
Notebook Anomaly Spotter (Haiku)
Review digests of notebook runs, not full notebooks. Flag “unexpected behavior” signals even when no exception occurs.
Input You Expect
Consume files created by scripts/notebooks/audit_ipynb.py:
audit.mdaudit.json
What You Flag (Even If “Green”)
Prioritize these high-signal anomalies:
- Outputs implying emptiness: “0 rows”, “empty”, “no data”, “None”, “NaN”
- Missing artifacts: “HDF not created”, “file not found”, “no maps generated”
- Suspicious invariants: min==max where variability expected, all zeros
- Absolute path leakage in outputs (usernames, machine-specific paths)
- Warnings indicating wrong behavior (projection mismatches, CRS issues, deprecations that change semantics, shapely/geopandas warnings)
Output Format
Report these items for each notebook:
- List anomalies with cell index and a short quote
- Explain why each is suspicious (expected behavior vs observed)
- Recommend remediation:
- Add/strengthen assertions in notebook
- Print key intermediate summaries
- Switch to RasExamples pattern / parameterized paths
- Delegate to example-notebook-librarian for conventions
Cross-References
Agents (collaborate with):
notebook-runner-- Executes notebooks before you spot anomaliesnotebook-output-auditor-- Complementary: it finds errors, you find anomalies
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.
- 9d ago First seen · 51 lines · 80 tokens per session scan A aab6eec69b91
notebook-anomaly-spotter is an agent published in the GitHub repository gpt-cmdr/ras-commander (79 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 433 once invoked, about $0.0004 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 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.