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 commands/roberto-mello/lavra/changeloggit 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/commands/roberto-mello/lavra/changelog)<a href="https://agentmods.dev/commands/roberto-mello/lavra/changelog"><img src="https://agentmods.dev/badge/commands/roberto-mello/lavra/changelog.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.00014 | $0.01039 |
| Opus 5 | $0.00007 | $0.00519 |
| Sonnet 5 | $0.00003 | $0.00208 |
| Haiku 4.5 | $0.00001 | $0.00104 |
Grade A, and why
changelog scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# Post using curl How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Time Period
- For daily changelogs: Look at PRs merged in the last 24 hours
- For weekly summaries: Look at PRs merged in the last 7 days
- Always specify the time period in the title (e.g., "Daily" vs "Weekly")
- Default: Get the latest changes from the last day from the main branch of the repository
PR Analysis
Analyze the provided GitHub changes and related issues. Look for:
- New features that have been added
- Bug fixes that have been implemented
- Any other significant changes or improvements
- References to specific issues and their details
- Names of contributors who made the changes
- Use gh cli to lookup the PRs as well and the description of the PRs
- Check PR labels to identify feature type (feature, bug, chore, etc.)
- Look for breaking changes and highlight them prominently
- Include PR numbers for traceability
- Check if PRs are linked to issues and include issue context
Content Priorities
- Breaking changes (if any) - MUST be at the top
- User-facing features
- Critical bug fixes
- Performance improvements
- Developer experience improvements
- Documentation updates
Formatting Guidelines
Now, create a change log summary with the following guidelines:
- Keep it concise and to the point
- Highlight the most important changes first
- Group similar changes together (e.g., all new features, all bug fixes)
- Include issue references where applicable
- Mention the names of contributors, giving them credit for their work
- Add a touch of humor or playfulness to make it engaging
- Use emojis sparingly to add visual interest
- Keep total message under 2000 characters for Discord
- Use consistent emoji for each section
- Format code/technical terms in backticks
- Include PR numbers in parentheses (e.g., "Fixed login bug (#123)")
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 · 150 lines · 14 tokens per session scan A 083d7aa5ef58
changelog is a command published in the GitHub repository roberto-mello/lavra (50 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 1,039 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
template
Manage issue templates for streamlined issue creation.
sync
Synchronize issues with a configured Dolt remote.
dep
Manage dependencies between issues.
decision
Record, list, and manage project decisions with rationale tracking.
prime
Load AI-optimized workflow context for beads issue tracking.