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.
npx agentmods add rules/rajudandigam/agent-inspect/architecturegit 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.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 | $0.00070 | $0.00070 |
| Opus 5 | $0.00035 | $0.00035 |
| Sonnet 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 5d 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.
- 5d 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 (501 stars, last pushed today), licensed MIT. It adds 70 tokens to every session, about $0.0003 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 cursor rules, from other repositories
modern
You are an expert TypeScript developer working on PromptScript - a language and toolchain for standardizing AI instructions across enterprise organizations.
graftcode-typescript-node-nextjs
Mandatory Graftcode architecture rules for TypeScript / Node.js / Next.js — expose plain modules via Graftcode instead of REST/gRPC/Thrift.
vue-typescript-patterns
Cursor rule "vue-typescript-patterns" from soaring-xiongkulu/easyaiot, covering vue3 + typescript 开发规范, vue 组件规范, vue sfc 组件规范, typescript 规范 and 状态管理.
nextjs-typescript-app-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript integration.
ipynb-files
This file contains rules and prompts for handling Jupyter Notebook (.ipynb) files in Cursor IDE, which currently doesn't have native support for .ipynb files.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.