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 skills add Mburdo/knowledge_and_vibes --skill advancegit 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/advance)<a href="https://agentmods.dev/skills/mburdo/knowledge_and_vibes/advance"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/advance/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mburdo/knowledge_and_vibes/advance"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/advance.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.03018 |
| Opus 5.5 | $0.00017 | $0.01207 |
| Sonnet 5.5 | $0.00008 | $0.00604 |
| Haiku 4.5 | $0.00004 | $0.00302 |
Grade A, and why
advance 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 1mo 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 — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Advance — Bead Lifecycle
Complete bead lifecycle: discover → verify → claim → work → close. Direct execution.
Design rationale: This skill executes directly rather than spawning subagents because each step is a simple command sequence (~200 tokens each), not substantial analytical work. Per Lita research: "Simple agents achieve 97% of complex system performance with 15x less code." Subagent overhead would exceed actual work.
When This Applies
| Signal | Action |
|---|---|
| User says "next task" or "what's next" | Run discovery → claim |
| User says "/advance" | Run full protocol |
| Just finished a task | Close out, then discover |
| Starting work on a specific bead | Verify → claim |
| User says "claim" or "start" | Verify → claim |
| User says "done" or "close" | Run close protocol |
Tool Reference
Agent Mail (MCP)
| Tool | Purpose |
|---|---|
fetch_inbox(agent_name) |
Check for messages before claiming |
file_reservation_paths(paths, exclusive) |
Reserve files before editing |
release_file_reservations(agent_name) |
Release files after closing |
send_message(to, subject, body_md, thread_id) |
Announce [CLAIMED]/[CLOSED] |
Bash Commands
| Command | Purpose |
|---|---|
bd list --status in_progress --json |
Check for current work |
bd ready --json |
List available tasks |
bd update <id> --status in_progress --assignee NAME |
Claim task |
bd close <id> --reason "..." |
Close completed bead |
bd dep tree <id> |
View dependencies |
bd blocked |
View blocked tasks |
bv --robot-triage |
Get recommendations |
bv --robot-next |
Get single best task |
bv --robot-plan |
Get execution order |
cm context "task description" --json |
Get patterns before starting |
pytest |
Run tests before closing |
ubs --staged |
Security scan (MANDATORY) |
Execution Flow
Execute these steps directly. No subagents needed.
Step 1: Close Out Previous Work
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.
- 1mo ago First seen · 479 lines · 0 tokens per session scan A 62ddccc7acbd
advance is a skill published in the GitHub repository Mburdo/knowledge_and_vibes (44 stars, last pushed 10mo ago), licensed MIT. It adds 42 tokens to every session and 3,018 once invoked, about $0.0002 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…