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/nometria-logingit clone --depth 1 https://github.com/nometria/claude-code-pluginWrote 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/nometria/claude-code-plugin/nometria-login)<a href="https://agentmods.dev/commands/nometria/claude-code-plugin/nometria-login"><img src="https://agentmods.dev/badge/commands/nometria/claude-code-plugin/nometria-login.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.00008 | $0.00772 |
| Opus 5 | $0.00004 | $0.00386 |
| Sonnet 5 | $0.00002 | $0.00154 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade A, and why
nometria-login 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST https://app.nometria.com/listUserMigrations \ How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nometria Login
Help the user set up their Nometria API token for deployments.
Step 1: Check existing token
# Check environment (API key or JWT)
echo "API_KEY: $([ -n "$NOMETRIA_API_KEY" ] && echo 'set' || echo 'not set')"
echo "TOKEN: $([ -n "$NOMETRIA_TOKEN" ] && echo 'set' || echo 'not set')"
# Check .env
grep -s 'NOMETRIA_API_KEY\|NOMETRIA_TOKEN' .env .env.local 2>/dev/null && echo "Found in .env" || echo ".env: not found"
# Check nom CLI credentials
cat ~/.nometria/credentials.json 2>/dev/null && echo "Found ~/.nometria/credentials.json" || echo "~/.nometria/credentials.json: not found"
If a token already exists, tell the user they're already authenticated and show which source it was found in. Ask if they want to update it.
Step 2: Get the token
Tell the user:
To get your Nometria API key:
- Go to https://nometria.com/settings/api-keys
- Sign in to your account
- Click Generate New Key
- Copy the key and paste it here
Your key is stored locally and never sent anywhere except the Nometria API. Alternatively, you can use
nom loginfrom the CLI.
Wait for the user to provide the token. They will paste it in the chat.
Step 3: Validate the token
Once the user provides a token, validate it by making a test API call:
curl -s -X POST https://app.nometria.com/listUserMigrations \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <USER_TOKEN>" \
-d '{}'
If the response contains "success": true, the token is valid.
If it returns 401 or an error, tell the user the token is invalid and ask them to try again.
Step 4: Store the token
If the current directory has a .env file, append to it:
NOMETRIA_API_KEY=<key>
If no .env exists, create .env with the key.
Also check if .gitignore contains .env. If not, warn the user:
⚠️ Make sure
.envis in your.gitignoreto avoid committing your token.
Step 5: Create workspace config
If no nometria.json exists and the user has migrations, ask if they want to link this workspace to one of their apps. If yes, create nometria.json:
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.
- 3d ago First seen · 99 lines · 8 tokens per session scan A ed91fbaee143
nometria-login is a command published in the GitHub repository nometria/claude-code-plugin (3 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 772 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
git
Git operations with intelligent commit messages and workflow optimization.
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.