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/antosubash/simplemodule/module-statusgit clone --depth 1 https://github.com/antosubash/SimpleModuleWrote 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/antosubash/simplemodule/module-status)<a href="https://agentmods.dev/commands/antosubash/simplemodule/module-status"><img src="https://agentmods.dev/badge/commands/antosubash/simplemodule/module-status.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.01621 |
| Opus 5 | $0.00000 | $0.00811 |
| Sonnet 5 | $0.00000 | $0.00324 |
| Haiku 4.5 | $0.00000 | $0.00162 |
Grade A, and why
module-status 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 today.
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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/module-status
Print a health snapshot of a SimpleModule module. No builds required — reads and greps only.
Step 0 — Resolve Module Name
If no argument was supplied, ask: "Which module would you like to inspect? (e.g., Products, Orders, Users)"
Use the provided name as {Name} throughout. Construct the paths:
CONTRACTS = modules/{Name}/src/SimpleModule.{Name}.Contracts/IMPL = modules/{Name}/src/SimpleModule.{Name}/TESTS = modules/{Name}/tests/SimpleModule.{Name}.Tests/
First, verify that IMPL exists by checking if {Name}Module.cs or any .csproj is present at that path. If not, note: "Note: The implementation directory may use a non-standard name. Check modules/{Name}/src/ to find the correct directory name and adjust paths accordingly."
Step 1 — Inventory
API Endpoints
Use Glob with pattern modules/{Name}/src/SimpleModule.{Name}/Endpoints/**/*Endpoint.cs. Count the results and collect the bare file names (strip path and .cs).
View Endpoints
Use Glob with pattern modules/{Name}/src/SimpleModule.{Name}/Views/**/*Endpoint.cs. Count and collect bare names. Note whether any view endpoints exist — this drives Sections 2 and 5.
Entities
Check whether modules/{Name}/src/SimpleModule.{Name}/EntityConfigurations/ exists. If it does, grep for HasKey( in that directory (all .cs files). For each matching file, derive the entity name by stripping Configuration from the class name (e.g., ProductConfiguration → Product). If the directory does not exist, note "N/A — no EntityConfigurations directory".
Domain Events
Grep for : IEvent in modules/{Name}/src/SimpleModule.{Name}.Contracts/ (all .cs files). Extract the record name from each match. List them; if none, show 0.
Services
Grep for class\s+\w+\s*:\s*I\w+Contracts in modules/{Name}/src/SimpleModule.{Name}/ (all .cs files). List each class name found. If no matches found, show "none detected".
Step 2 — Page Registry Coverage
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.
- today First seen · 132 lines · 0 tokens per session scan A 385fbed7a545
module-status is a command published in the GitHub repository antosubash/SimpleModule (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,621 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-09-04.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.