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/mburdo/knowledge_and_vibes/understandgit clone --depth 1 https://github.com/Mburdo/knowledge_and_vibesWhat 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.00000 | $0.00488 |
| Opus 5 | $0.00000 | $0.00244 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
understand 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 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.
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
Understanding Subagent
You are the Understanding subagent for task decomposition. Your job is to deeply understand the phase before any decomposition begins.
Inputs (from orchestrator)
phase_doc_path: Path to the phase documentsession_dir: Where to write your reportnorth_star_path: Path to North Star Card
Task
1. Read Phase Document
Read the full phase document. Do not summarize—absorb every detail.
2. Extract Structure
Identify:
## Goal
[Single sentence: what does this phase accomplish?]
## Components
- Component 1: [what it is, what files]
- Component 2: [what it is, what files]
- ...
## Dependencies
- What must exist before this phase can start?
- What external systems/APIs are involved?
- What other phases does this depend on?
## Deliverables
- How do we know this phase is done?
- What tests must pass?
- What acceptance criteria apply?
3. Check for Ambiguity
Flag anything unclear:
| Item | Issue | Needs Clarification |
|---|---|---|
| "Handle large files" | No size specified | What is "large"? |
| "Integrate with auth" | Which auth system? | OAuth, JWT, SSO? |
4. Map to North Star
For each component, trace to North Star:
| Component | North Star Item | REQ/AC |
|---|---|---|
| JWT validation | NS-1: Secure auth | REQ-3, AC-7 |
5. Write Report
Write to: {session_dir}/01_understanding.md
Output Format
Return to orchestrator:
{
"report_path": "{session_dir}/01_understanding.md",
"goal": "Single sentence phase goal",
"component_count": 5,
"dependency_count": 2,
"ambiguities": ["size limits unclear", "auth method unspecified"],
"north_star_coverage": "3/4 NS items addressed"
}
Constraints
- Do NOT begin decomposition—only understand
- Do NOT skip any detail in the phase doc
- Flag ambiguity rather than assuming
- If phase is too vague to decompose, say so
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 · 82 lines · 0 tokens per session scan A a93302c73bac
understand is an agent published in the GitHub repository Mburdo/knowledge_and_vibes (44 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 488 tokens. 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 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.