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/anivaryam/anivaryam-plugins/diffgit clone --depth 1 https://github.com/anivaryam/anivaryam-pluginsWhat 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.00022 | $0.00240 |
| Opus 5 | $0.00011 | $0.00120 |
| Sonnet 5 | $0.00004 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
diff 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 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.
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.
What it actually says
Run env-vault diff $ARGUMENTS.
Default: env-vault diff .env .env.vault.
By default the diff only shows key names. Pass --values to show the actual changed values — useful in private terminals, dangerous in shared ones. Warn the user before adding --values if the conversation context suggests a shared screen, CI logs, or anything pipe-able to an untrusted sink.
After running, group findings:
- Added keys (in
.env, missing in vault) → needs a re-seal. - Removed keys (in vault, missing in
.env) → either intentional pruning or an opened vault that has been edited; flag for the user. - Changed values → re-seal recommended.
If anything would benefit from re-sealing, recommend the exact command: env-vault seal .env -o .env.vault. Do not run it yourself unless asked.
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 · 19 lines · 22 tokens per session scan A 8ae47f7ae84c
diff is a command published in the GitHub repository anivaryam/anivaryam-plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 240 once invoked, about $0.0001 per session on Opus 5. 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-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.
constitution
Create or update the project constitution from interactive or provided principle inputs.