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/frankfmy/buddy-evolution/achievementsnpx skills add FrankFMY/buddy-evolution --skill achievementsgit clone --depth 1 https://github.com/FrankFMY/buddy-evolutionWrote 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/frankfmy/buddy-evolution/achievements)<a href="https://agentmods.dev/skills/frankfmy/buddy-evolution/achievements"><img src="https://agentmods.dev/badge/skills/frankfmy/buddy-evolution/achievements.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.00034 | $0.01138 |
| Opus 5 | $0.00017 | $0.00569 |
| Sonnet 5 | $0.00007 | $0.00228 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
achievements 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Buddy Achievements
Read the buddy soul file and display achievements organized by status.
Instructions
- Read
~/.buddy-evolution/soul.json - If the file doesn't exist, tell the user to start a new session first
- Categorize achievements and format as shown below
Achievement catalog (34 total, 2 hidden)
Coding
| ID | Name | Trigger | XP | Rarity |
|---|---|---|---|---|
| first_steps | First Steps | Complete first session | 100 | Common |
| getting_comfortable | Getting Comfortable | 10 sessions | 200 | Common |
| centurion | Centurion | 100 sessions | 1,000 | Uncommon |
| veteran | Veteran | 500 sessions | 3,000 | Rare |
| living_legend | Living Legend | 1,000 sessions | 10,000 | Legendary |
| the_architect | The Architect | 20+ file edits in one session | 500 | Rare |
| tool_master | Tool Master | 100+ tool calls in one session | 400 | Uncommon |
| wordsmith | Wordsmith | 100K+ output tokens in one session | 600 | Rare |
Testing
| ID | Name | Trigger | XP | Rarity |
|---|---|---|---|---|
| first_test | First Test | Run tests in a session | 100 | Common |
| test_enthusiast | Test Enthusiast | 10+ test runs | 300 | Uncommon |
| test_marathon | Test Marathon | 50+ test runs | 1,000 | Epic |
| test_driven | Test-Driven | Tests in 10 consecutive sessions | 800 | Rare |
Debugging
| ID | Name | Trigger | XP | Rarity |
|---|---|---|---|---|
| persistence | Persistence | 5+ rejected calls, still finish work | 300 | Uncommon |
| against_all_odds | Against All Odds | 20+ rejected calls, still finish work | 800 | Epic |
| unbreakable | Unbreakable | 0 rejected in 50+ call session | 500 | Rare |
| context_survivor | Context Survivor | Productive work after context reset | 400 | Uncommon |
Consistency
| ID | Name | Trigger | XP | Rarity |
|---|---|---|---|---|
| streak_week | Streak: Week | 7 consecutive days | 500 | Common |
| streak_month | Streak: Month | 30 consecutive days | 2,000 | Rare |
| streak_quarter | Streak: Quarter | 90 consecutive days | 5,000 | Epic |
| streak_year | Streak: Year | 365 consecutive days | 20,000 | Legendary |
| early_bird | Early Bird ♻️ | Session before 7 AM | 100 | Common |
| night_owl | Night Owl ♻️ | Session past midnight | 100 | Common |
| marathon | Marathon | 4+ hour session | 600 | Rare |
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 · 101 lines · 34 tokens per session scan A 047cf9401d96
achievements is a skill published in the GitHub repository FrankFMY/buddy-evolution (5 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,138 once invoked, about $0.0002 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-31.
Other skills, from other repositories
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
add-teams
Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.
sys-configure
Configure Claude Octopus — redirects to /octo:setup interactive wizard.
recipe-reverse-engineer
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
37signals-way
Build lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat…