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/rajudandigam/agent-inspectWrote 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/rules/rajudandigam/agent-inspect/architecture)<a href="https://agentmods.dev/rules/rajudandigam/agent-inspect/architecture"><img src="https://agentmods.dev/badge/rules/rajudandigam/agent-inspect/architecture/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/rules/rajudandigam/agent-inspect/architecture"><img src="https://agentmods.dev/badge/rules/rajudandigam/agent-inspect/architecture.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.00070 | $0.00070 |
| Opus 5.5 | $0.00028 | $0.00028 |
| Sonnet 5.5 | $0.00014 | $0.00014 |
| Haiku 4.5 | $0.00007 | $0.00007 |
Grade A, and why
architecture 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.
What it actually says
agent-inspect
agent-inspect is a local-first execution-tree debugger for TypeScript AI agents. Before implementing or reviewing features, read the repo’s top-level docs (starting with README.md) and follow the established MVP scope and guardrails.
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 First seen · 9 lines · 70 tokens per session scan A 367e56506a81
architecture is a cursor rule published in the GitHub repository rajudandigam/agent-inspect (165 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session, about $0.0003 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 cursor rules, from other repositories
rewynd
Debug and verify backend runtime behavior (HTTP 500s, wrong responses, slow endpoints, suspected N+1 or duplicate queries) by reading the actual recorded request trace via rewynd, instead of guessing from source or adding print statements.
explicit-opt-in-over-diagnostics
Prefer requiring explicit opt-in over emitting diagnostics on intentional user paths.
code-style
Formatting, lint, comments language.
handle-unexpected-errors-by-inspecting-the-cause
Cursor rule "handle-unexpected-errors-by-inspecting-the-cause" from PaulJPhilp/EffectPatterns, covering handle unexpected errors by inspecting the cause and example.
bundling
The project uses a custom type bundling system to provide full TypeScript IntelliSense support in the Monaco editor for @bubblelab/bubble-core and its dependencies. This is necessary because Monaco cannot directly resolve workspace packages or external dependencies.
modus-checkbox-value-inversion-react
Critical bug fix for ModusWcCheckbox value property inversion.