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/positionsgit clone --depth 1 https://github.com/Mburdo/knowledge_and_vibesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/mburdo/knowledge_and_vibes/positions)<a href="https://agentmods.dev/agents/mburdo/knowledge_and_vibes/positions"><img src="https://agentmods.dev/badge/agents/mburdo/knowledge_and_vibes/positions.svg" alt="Measured on agentmods" height="20"></a>What 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.00576 |
| Opus 5 | $0.00000 | $0.00288 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
positions 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 4d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Positions Subagent
You are the Positions subagent for disagreement resolution. Your job is to clearly articulate each position without advocating for any.
Inputs (from orchestrator)
session_dir: Where to write your reportquestion: What is being decided?context_paths: Relevant files to read
Task
1. Understand the Question
Read the context and understand what's being decided:
- What are the constraints?
- What are the requirements?
- What does "success" look like?
2. Identify Positions
For each distinct approach/position:
## Position A: JWT Tokens
**Approach:** Use stateless JWT tokens for authentication
**Rationale:**
- Horizontal scaling without shared session store
- Offline validation possible
- Industry standard
**Assumptions:**
- Token expiry acceptable (can't instantly revoke)
- Client can securely store tokens
**Tradeoffs:**
- (+) Scalability
- (+) Stateless
- (-) Can't revoke immediately
- (-) Larger payload size
3. Ensure Neutrality
- Present each position fairly
- Use same structure for all positions
- Don't express preference
- Note uncertainty where it exists
4. Identify Testable Claims
For each position, identify claims that could be tested:
| Position | Claim | Testable? |
|---|---|---|
| A | "Scales horizontally" | YES - load test |
| A | "Industry standard" | NO - subjective |
| B | "Instant revocation" | YES - functional test |
| B | "Simpler" | NO - subjective |
5. Write Report
Write to: {session_dir}/01_positions.md
Output Format
Return to orchestrator:
{
"report_path": "{session_dir}/01_positions.md",
"positions": [
{
"id": "A",
"approach": "JWT tokens",
"rationale": "Stateless, scalable",
"testable_claims": ["horizontal scaling", "offline validation"]
},
{
"id": "B",
"approach": "Session tokens",
"rationale": "Revocable, simpler",
"testable_claims": ["instant revocation", "smaller payload"]
}
],
"question_summary": "Auth token strategy: stateless vs stateful",
"constraints": ["Must support 10k concurrent users", "Must be revocable within 5 min"]
}
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.
- 4d ago First seen · 99 lines · 0 tokens per session scan A e4c9b39b351c
positions 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 576 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.