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/deploygit 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.01215 |
| Opus 5 | $0.00005 | $0.00607 |
| Sonnet 5 | $0.00002 | $0.00243 |
| Haiku 4.5 | $0.00001 | $0.00121 |
Grade A, and why
deploy 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(sleep:*), Bash(echo:*), Bash(grep:*), Read, Write How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy to Production
You are deploying the user's app to production via the Nometria platform. Execute this workflow precisely.
Step 1: Resolve API token
Find the Nometria API token. Check in this order:
# 1. Environment variables (API key or JWT token)
echo "$NOMETRIA_API_KEY"
echo "$NOMETRIA_TOKEN"
# 2. .env file in current project
grep -s 'NOMETRIA_API_KEY\|NOMETRIA_TOKEN' .env .env.local 2>/dev/null
# 3. Stored credentials from `nom login`
cat ~/.nometria/credentials.json 2>/dev/null
# 4. Home directory config (legacy)
cat ~/.nometria 2>/dev/null
If no token is found, tell the user:
No Nometria API token found. Run
nom loginor/nometria-loginto authenticate. Get your API key at https://nometria.com/settings/api-keys
Stop here if no token. Do not proceed without a valid token.
Store the token: TOKEN="<the token>"
Step 2: Identify the app
Check if there's a nometria.json in the workspace root:
cat nometria.json 2>/dev/null
If it exists, extract app_id and migration_id from it.
If not, or if the user specified an app name as $ARGUMENTS, list all migrations:
curl -s -X POST https://app.nometria.com/listUserMigrations \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $TOKEN" \
-d '{}'
From the response, find the matching migration. If multiple apps exist and the user didn't specify which one, show a numbered list and ask them to pick:
1. MyApp (Base44) - hosting, paid
2. OtherApp (Lovable) - hosting, paid
3. TestApp (Manus) - download, pending
Only proceed with migrations that have delivery_type: "hosting" and payment_status: "paid".
Store: APP_ID="<app_id>" and MIGRATION_ID="<migration_id>"
Step 3: Check current deployment status
curl -s -X POST https://app.nometria.com/checkAwsStatus \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $TOKEN" \
-d "{\"app_id\": \"$APP_ID\"}"
Parse the response to determine the instance state.
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 · 164 lines · 9 tokens per session scan A 70441f271fde
deploy 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 1,215 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.