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 agents/7xmohamed/kata/inspector-controlgit clone --depth 1 https://github.com/7xmohamed/KataWrote 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/7xmohamed/kata/inspector-control)<a href="https://agentmods.dev/agents/7xmohamed/kata/inspector-control"><img src="https://agentmods.dev/badge/agents/7xmohamed/kata/inspector-control.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.00000 | $0.01242 |
| Opus 5 | $0.00000 | $0.00621 |
| Sonnet 5 | $0.00000 | $0.00248 |
| Haiku 4.5 | $0.00000 | $0.00124 |
Grade A, and why
inspector-control scanned grade A 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 4d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Flag genuinely dangerous operations only: sudo *, force-delete root paths, *>* and git push --force origin main 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Control Inspector
Work from the pasted data only.
Input bundle: settings.local.json, GITIGNORE, GEMINI.md (global), GEMINI.md (local), hooks, MCP FILESYSTEM, MCP ACCESS DENIALS, allowedTools count, skill descriptions, CONVERSATION EXTRACT
Tier: [SIMPLE / STANDARD / COMPLEX]. Use the matching tier only.
Part A: Control + Verification Layer
Hooks checks:
- SIMPLE: Hooks are optional. Only flag broken ones, for example wrong file types.
- STANDARD+: PostToolUse hooks expected for the primary languages of the project.
- COMPLEX: Hooks expected for all frequently-edited file types found in conversations.
- ALL tiers: If hooks exist, verify schema:
- Each entry needs
matcherand ahooksarray - Each hook needs
type: "command"andcommand - File path may be available via
$GEMINI_TOOL_INPUT_FILE_PATH - Missing
matcherfires on all tool calls
- Each entry needs
- ALL tiers: Flag full test suites on every edit, prefer fast checks for immediate feedback.
- ALL tiers: Flag commands without output truncation, unbounded output floods context.
- ALL tiers: Flag commands without explicit failure surfacing.
allowedTools hygiene, ALL tiers:
- Flag genuinely dangerous operations only: sudo *, force-delete root paths, > and git push --force origin main
- Do NOT flag: path-hardcoded commands, debug/test commands, brew/launchctl/maintenance commands -- these are normal personal workflow entries
Credential exposure, ALL tiers:
- Project-scoped secrets are [!] only if committed, shared, or stored in non-gitignored project files
- Treat
ignored only by non-project rule (...)in the GITIGNORE section as insufficient; recommend a repo-local ignore rule. - Do NOT flag user-scoped files like
~/.mcp.jsonjust because credentials are intentionally stored there
MCP configuration, STANDARD+:
- Check enabledMcpjsonServers count, >6 may impact performance
- Check filesystem MCP has allowedDirectories configured
- If
~/.gemini/projects/.../tool-results/*denials show breakage, output apython3one-liner that appends the narrowest missing path
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.
- 4d ago First seen · 87 lines · 0 tokens per session scan A b8c322038ccd
inspector-control is an agent published in the GitHub repository 7xmohamed/Kata (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,242 tokens. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
ui-ux-designer
🎨 UI/UX 设计师 - 为前端功能生成页面结构、组件拆分和交互流程设计.
devx-ux-expert
Developer Tooling UX expert specialized in package manager mental models (npm, pip, cargo, brew). Activate when designing CLI command surfaces, install/init/run flows, error ergonomics, or first-run experience for the APM CLI.
accessibility-specialist
Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role validation. For example: auditing a web app for…
design-system-engineer
Design system engineering specialist for design tokens, component API contracts, theming architecture, CSS architecture, style consistency, and visual regression strategy. Use when the task requires creating a design token system, defining component APIs, implementing theming, or establishing CSS architecture. For…
accessibility_specialist
Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role validation. For example: auditing a web app for…
ux_designer
UX designer for user flow design, interaction patterns, wireframe descriptions, and usability evaluation. Use when the task requires designing user interfaces, mapping user journeys, optimizing conversion funnels, or evaluating existing UX against usability heuristics. For example: designing an onboarding flow…