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/nometria/claude-code-plugin/statusgit clone --depth 1 https://github.com/nometria/claude-code-pluginWhat 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.00009 | $0.00672 |
| Opus 5 | $0.00005 | $0.00336 |
| Sonnet 5 | $0.00002 | $0.00134 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
status 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(curl:*), Bash(cat:*), Bash(grep:*), Bash(echo:*), Read How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Deployment Status
Show the user the current state of their Nometria deployments.
Step 1: Resolve token
TOKEN="${NOMETRIA_API_KEY:-${NOMETRIA_TOKEN:-$(grep -s 'NOMETRIA_API_KEY\|NOMETRIA_TOKEN' .env .env.local 2>/dev/null | head -1 | cut -d= -f2- | tr -d ' "'"'"'')}}"
If no token: tell the user to run /nometria-login and stop.
Step 2: List all migrations
curl -s -X POST https://app.nometria.com/listUserMigrations \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $TOKEN" \
-d '{}'
Step 3: Check AWS status for hosting apps
For each migration with delivery_type: "hosting", check its status:
curl -s -X POST https://app.nometria.com/checkAwsStatus \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $TOKEN" \
-d "{\"app_id\": \"<APP_ID>\"}"
Step 4: Display formatted table
Present results as a clear table:
╔══════════════════╦══════════╦═══════════╦════════════════════════════════╦═════════════════╗
║ App ║ Platform ║ Status ║ URL ║ Instance ║
╠══════════════════╬══════════╬═══════════╬════════════════════════════════╬═════════════════╣
║ MyApp ║ Base44 ║ ● running ║ https://myapp.nometria.com ║ 4gb (t4g.med) ║
║ OtherApp ║ Lovable ║ ○ stopped ║ https://otherapp.nometria.com ║ 2gb (t4g.small) ║
║ TestProject ║ Manus ║ - none ║ - ║ - ║
╚══════════════════╩══════════╩═══════════╩════════════════════════════════╩═════════════════╝
Use these status indicators:
● running- app is live◐ deploying/◐ launching- deployment in progress○ stopped- instance exists but is off✕ failed- deployment failed (show error if available)- none- not deployed to hosting
If $ARGUMENTS was provided, filter the results to match that app name.
Also show:
- Total apps: X
- Running: X
- Stopped: X
If there's a nometria.json in the workspace, highlight the linked app with ← linked.
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.
- yesterday First seen · 70 lines · 9 tokens per session scan A d6a961c0a6fd
status is a command published in the GitHub repository nometria/claude-code-plugin (3 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 672 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.