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 roberto-mello/lavra --skill lavra-work-singlegit clone --depth 1 https://github.com/roberto-mello/lavraWrote 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/roberto-mello/lavra/lavra-work-single)<a href="https://agentmods.dev/skills/roberto-mello/lavra/lavra-work-single"><img src="https://agentmods.dev/badge/skills/roberto-mello/lavra/lavra-work-single/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/roberto-mello/lavra/lavra-work-single"><img src="https://agentmods.dev/badge/skills/roberto-mello/lavra/lavra-work-single.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.00037 | $0.05512 |
| Opus 5 | $0.00018 | $0.02756 |
| Sonnet 5 | $0.00007 | $0.01102 |
| Haiku 4.5 | $0.00004 | $0.00551 |
Grade B, and why
lavra-work-single scanned grade B with 1 finding 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 9d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls .claude/skills/ 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 555 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SINGLE-BEAD PATH
Used when exactly one bead is being worked on. Full-quality interactive flow with built-in review, fix loop, and learn phases.
State machine: IMPLEMENTING -> REVIEWING -> FIXING -> RE_REVIEWING -> LEARNING -> DONE
Flags:
--skip-review: skip the/lavra-reviewsubagent call in Phase 3 step 3. Self-review (step 2) still runs. Used by the sequential epic loop, which runs a single review pass after all beads complete.EPIC_PLAN={...}: epic locked decisions injected by the sequential loop. Treat identically to a parent epic read in Phase 1 step 1.
<project_root>
All .lavra/ paths are relative to the project root. PROJECT_ROOT may be injected into your context — use it if set. If not, resolve it once and reuse:
PROJECT_ROOT="${PROJECT_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || echo "$PWD")}"
Then prefix all .lavra/ paths with "$PROJECT_ROOT/" when invoking them via Bash.
</project_root>
Phase 1: Quick Start
-
Read Bead and Clarify
If a bead ID was provided:
bd show {BEAD_ID} --longRead the bead description completely including:
- What section (implementation requirements)
- Context section (research findings, constraints)
- Decisions section (Locked = must honor, Discretion = agent's flexibility budget, Deferred = do NOT implement)
- Testing section (test cases to implement)
- Validation section (acceptance criteria)
- Dependencies section (blockers)
- Comments (INVESTIGATION/FACT/PATTERN/DECISION/LEARNED from research phase -- treat as implementation constraints with the same weight as Locked Decisions)
If the bead has a parent epic, also read the epic's decision sections:
bd show {BEAD_ID} --json | jq -r '.[0].parent // empty' # If parent exists: bd show {PARENT_EPIC_ID}Extract
## Locked Decisions,## Agent Discretion, and## Deferredsections. Locked = must honor. Discretion = deviation budget. Deferred = do NOT implement (these are explicitly out of scope).
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.
- 9d ago First seen · 555 lines · 37 tokens per session scan B f6a3c5409d9d
lavra-work-single is a skill published in the GitHub repository roberto-mello/lavra (51 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 5,512 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
python-package-management
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.