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 commands/opensesh/karimo-overview/audit-devpropsgit clone --depth 1 https://github.com/opensesh/karimo-overviewWrote 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/commands/opensesh/karimo-overview/audit-devprops)<a href="https://agentmods.dev/commands/opensesh/karimo-overview/audit-devprops"><img src="https://agentmods.dev/badge/commands/opensesh/karimo-overview/audit-devprops.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.01329 |
| Opus 5 | $0.00000 | $0.00665 |
| Sonnet 5 | $0.00000 | $0.00266 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
audit-devprops 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit-devprops — devProps Compliance Audit
Scan the codebase for devProps compliance and produce a structured report grouped by section, with a percentage summary and an explicit exemption list.
Usage
/audit-devprops
This command is read-only and never modifies files.
Behavior
Run the following steps in order. Use the Grep tool (not Bash) for all searches.
Step 1: Find compliant files
Use Grep to find all .tsx files under app/ and components/ that call devProps:
- Pattern:
devProps\( - Paths:
app/,components/ - File type:
tsx - Output mode:
files_with_matches
Record this as your compliant set.
Step 2: Find all potential component files
Use Grep to find all .tsx files under app/ and components/ that export a PascalCase component:
- Pattern:
export (default )?(function|const) [A-Z] - Paths:
app/,components/ - File type:
tsx - Output mode:
files_with_matches
Record this as your component set.
Step 3: Identify non-compliant files
Compare the two sets. Files in the component set that are NOT in the compliant set are non-compliant. Exclude:
- Files in
lib/,hooks/,types/,utils/— these are not components - Known exemptions listed in Step 6 below
Step 4: Group results by section
Organize all files (both compliant and non-compliant) into these sections based on their path:
| Section | Path prefix |
|---|---|
app/ pages |
app/ files that are page.tsx |
app/ layouts |
app/ files that are layout.tsx or template.tsx |
app/ other |
other app/ files |
components/home/ |
components/home/ |
components/layout/ |
components/layout/ |
components/shared/ |
components/shared/ |
components/projects/ |
components/projects/ |
components/blog/ |
components/blog/ |
components/about/ |
components/about/ |
components/three/ |
components/three/ |
components/providers/ |
components/providers/ |
| Other | any remaining components/ subdirectories |
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 · 143 lines · 0 tokens per session scan A d806ca5dbbc0
audit-devprops is a command published in the GitHub repository opensesh/karimo-overview (11 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,329 tokens. 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 commands, from other repositories
doctor
Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
run
Execute an approved PRD using feature branch workflow (v7.0). This command generates briefs, auto-reviews them, allows user iteration, and then orchestrates execution.
merge
Consolidate feature branch changes and create final PR to main. This completes the v5.0 feature branch workflow after all task PRs have been merged.
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.
feedback
Intelligent feedback capture with automatic complexity detection and adaptive investigation.