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 skills/mburdo/knowledge_and_vibes/agent-mailnpx skills add Mburdo/knowledge_and_vibes --skill agent-mailgit 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/skills/mburdo/knowledge_and_vibes/agent-mail)<a href="https://agentmods.dev/skills/mburdo/knowledge_and_vibes/agent-mail"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/agent-mail.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.1 | $0.00050 | $0.01559 |
| Opus 5 | $0.00025 | $0.00779 |
| Sonnet 5 | $0.00010 | $0.00312 |
| Haiku 4.5 | $0.00005 | $0.00156 |
Grade A, and why
agent-mail 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 6d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Mail (MCP Server)
Multi-agent coordination: registration, file reservations, messaging, and build slots.
When This Applies
| Signal | Action |
|---|---|
| Starting a session | ensure_project + register_agent |
| Before editing files | file_reservation_paths |
| Communicating with agents | send_message / fetch_inbox |
| Finishing work | release_file_reservations |
Registration (Required First)
# 1. Ensure project exists
ensure_project(human_key="/abs/path/to/project")
# 2. Register yourself (auto-generates name like "GreenCastle")
register_agent(
project_key="/abs/path/to/project",
program="claude-code",
model="opus-4.5",
task_description="Working on feature X"
)
# SAVE the returned agent name!
# 3. Set contact policy
set_contact_policy(
project_key="/abs/path/to/project",
agent_name="YOUR_AGENT_NAME",
policy="open"
)
File Reservations
Reserve before editing:
file_reservation_paths(
project_key="/abs/path",
agent_name="YourName",
paths=["src/module/**", "tests/test_module.py"],
ttl_seconds=3600,
exclusive=True,
reason="bd-123: implementing feature"
)
Extend if needed:
renew_file_reservations(
project_key="/abs/path",
agent_name="YourName",
extend_seconds=1800
)
Release when done:
release_file_reservations(
project_key="/abs/path",
agent_name="YourName"
)
Messaging
Send message:
send_message(
project_key="/abs/path",
sender_name="YourName",
to=["OtherAgent"],
subject="[CLAIMED] bd-123 - Feature Title",
body_md="Starting work on **bd-123**.\n\nFile reservations: `src/module/**`",
thread_id="bd-123",
importance="normal" # low, normal, high, urgent
)
Reply:
reply_message(
project_key="/abs/path",
message_id=123,
sender_name="YourName",
body_md="Acknowledged. Proceeding."
)
Check inbox:
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.
- 6d ago First seen · 298 lines · 50 tokens per session scan A 6ffebe700f62
agent-mail is a skill published in the GitHub repository Mburdo/knowledge_and_vibes (44 stars, last pushed 8mo ago), licensed MIT. It adds 50 tokens to every session and 1,559 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…