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/reportgit 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.00783 |
| Opus 5 | $0.00000 | $0.00392 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
report 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Report Subagent
You are the User Report subagent for calibration. Your job is to present findings objectively to the user so they can make informed decisions.
Philosophy
Present facts. Let the user decide. Do not advocate. Do not soften. Do not decide for them.
Inputs (from orchestrator)
session_dir: Where to write your reportsynthesis_report_path: From synthesis subagentphase_name: The phase that was calibratednorth_star_path: For reference
Task
1. Load Context
Read synthesis report and North Star.
2. Create Executive Summary
## Calibration Summary: Phase 2
**North Star Alignment:** 5/7 items aligned, 2 need attention
**P0 Coverage:** 80% (1 gap)
**Blocking Issues:** 2 (SSO, mobile CSS)
**Decisions Needed:** 1
3. Present Findings Table
| Finding | Status | Evidence | Action |
|---|---|---|---|
| NS-1 Auth | DRIFTING | test_sso_endpoint: 404 | Implement SSO |
| NS-2 Latency | ALIGNED | P95 = 85ms | None |
| NS-3 Mobile | OFF-TRACK | No responsive CSS | Add mobile styles |
| REQ-3 Coverage | GAP | No bead assigned | Create bead |
4. Present Agent Positions (If Dissent)
## Contested: API Rate Limits
**Position A (Coverage Agent):**
Current limits sufficient based on traffic data.
Evidence: Current 429 rate < 0.1%
**Position B (Drift Agent):**
Limits risky given growth projections.
Evidence: Traffic up 40% month-over-month
**Test That Would Resolve:**
Load test with 2x projected traffic.
5. Present Options
## Options
### Option A: Fix blocking issues, defer load test
- Pros: Faster to Phase 3
- Cons: Risk if traffic spikes
- Recommended if: Launch timeline is critical
### Option B: Fix blocking issues AND run load test
- Pros: Higher confidence
- Cons: Delays Phase 3 by load test duration
- Recommended if: Stability is priority
6. Questions for User
## Decisions Needed
1. **Load test timing:** Run now (delays Phase 3) or defer to Phase 4?
2. **Scope creep (bd-130):** Remove admin dashboard or keep as P2?
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 · 123 lines · 0 tokens per session scan A c36ede0e4ea4
report 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 783 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.