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/dnyoussef/context-cascade/verix-command-templategit clone --depth 1 https://github.com/DNYoussef/context-cascadeWhat 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.00014 | $0.00889 |
| Opus 5 | $0.00007 | $0.00445 |
| Sonnet 5 | $0.00003 | $0.00178 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
VERIX-COMMAND-TEMPLATE 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 2d 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.
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Library-First Directive
This agent operates under library-first constraints:
-
Pre-Check Required: Before writing code, search:
.claude/library/catalog.json(components).claude/docs/inventories/LIBRARY-PATTERNS-GUIDE.md(patterns)D:\Projects\*(existing implementations)
-
Decision Matrix:
Result Action Library >90% REUSE directly Library 70-90% ADAPT minimally Pattern documented FOLLOW pattern In existing project EXTRACT and adapt No match BUILD new
Library-First Directive
This agent operates under library-first constraints:
-
Pre-Check Required: Before writing code, search:
.claude/library/catalog.json(components).claude/docs/inventories/LIBRARY-PATTERNS-GUIDE.md(patterns)D:\Projects\*(existing implementations)
-
Decision Matrix:
Result Action Library >90% REUSE directly Library 70-90% ADAPT minimally Pattern documented FOLLOW pattern In existing project EXTRACT and adapt No match BUILD new
STANDARD OPERATING PROCEDURE
Purpose
- Primary action: {what this command does}
Trigger Conditions
- Command syntax: /VERIX-COMMAND-TEMPLATE [args]
- Ensure prerequisites are met before execution.
Inputs and Options
- Inputs: No structured parameters defined; capture user intent explicitly.
Execution Phases
- Review the request and confirm scope.
- Execute the command flow.
- Summarize outcomes and next actions.
Success Criteria and Outputs
- Document artifacts, decisions, and follow-up actions clearly.
Error Handling and Recovery
- If execution fails, capture the failure mode, retry with verbose context, and surface actionable remediation steps.
Chaining and Coordination
Memory and Tagging
- Tag session outputs with who/when/why for traceability.
Example Invocation
- /VERIX-COMMAND-TEMPLATE example
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.
- 2d ago First seen · 113 lines · 14 tokens per session scan A f479af4723e9
VERIX-COMMAND-TEMPLATE is a command published in the GitHub repository DNYoussef/context-cascade (32 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 889 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-30.
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.