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 agents/dnyoussef/context-cascade/agent-typesgit 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.00005 | $0.00879 |
| Opus 5 | $0.00003 | $0.00439 |
| Sonnet 5 | $0.00001 | $0.00176 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
agent-types 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.
This is a copy
91% identical to agent-capabilities — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 115 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: Primary input
Trigger Conditions
- Command syntax: /agent-types [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
- /agent-types example
Output Format
- Provide a concise summary, actions taken, artifacts generated, and recommended next steps.
- Always include an explicit confidence line: "Confidence: X.XX (ceiling: TYPE Y.YY)".
- Use ceilings — inference/report: 0.70, research: 0.85, observation: 0.95, definition: 0.95.
- Keep user-facing output in plain English; reserve VCL markers for the appendix only.
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 · 115 lines · 5 tokens per session scan A 2126a55e2820
agent-types is an agent published in the GitHub repository DNYoussef/context-cascade (32 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 879 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to agent-capabilities, differing in 10 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.