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 kulmam92/cc-best-practices-marketplace --skill bp-learngit clone --depth 1 https://github.com/kulmam92/cc-best-practices-marketplaceWrote 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/kulmam92/cc-best-practices-marketplace/bp-learn)<a href="https://agentmods.dev/skills/kulmam92/cc-best-practices-marketplace/bp-learn"><img src="https://agentmods.dev/badge/skills/kulmam92/cc-best-practices-marketplace/bp-learn/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/kulmam92/cc-best-practices-marketplace/bp-learn"><img src="https://agentmods.dev/badge/skills/kulmam92/cc-best-practices-marketplace/bp-learn.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.00067 | $0.01132 |
| Opus 5 | $0.00034 | $0.00566 |
| Sonnet 5 | $0.00013 | $0.00226 |
| Haiku 4.5 | $0.00007 | $0.00113 |
Grade A, and why
bp-learn 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 11d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Rule Capture -- Compounding Engineering
Turn every code review, debugging session, and incident into a permanent team-wide improvement. This is Boris Cherny's "compounding engineering" -- every session benefits from all previous sessions' learnings.
Auto-memory handles personal learnings automatically. This skill is for team-shared rules committed to git so the whole team benefits.
Steps
- Parse the rule from the provided arguments. Understand what convention, anti-pattern, or guard rail needs to be captured.
1b. Check correction context -- If this rule came from a correction or debugging session, mention Boris's golden rule: "After every correction, capture the lesson so it never happens again." If the pattern is mechanically enforceable (e.g., SQL conventions, import ordering, naming patterns), strongly suggest a lint rule (option c) -- enforcement always beats advice.
-
Detect scope -- is this rule project-wide or component-specific?
- Check if the project has multiple components (look for subdirectory CLAUDE.md files or common multi-component layouts like frontend/, backend/, infra/, packages/)
- If multi-component: ask "Is this rule for the whole project, or specific to [detected components]?"
- If single-component: skip -- it's project-wide
-
Auto-select output target based on project structure (do NOT ask):
- Single-component project → write to CLAUDE.md
- Multi-component project → write to
.claude/rules/<topic>.md(project-wide) or.claude/rules/<component>-<topic>.mdwithpathsfrontmatter (component-specific) - If CLAUDE.md is at ~150+ lines → automatically use
.claude/rules/instead and note why - If a linter is detected and the pattern is mechanically enforceable → suggest a lint rule as well
- Mention graduation path inline: "This is an advisory rule. If it keeps recurring, graduate to a lint rule or hook via /bp-audit."
Only ask the user to choose a target if:
- The rule could reasonably go to multiple components
- The user explicitly requests a different target
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.
- 11d ago First seen · 83 lines · 67 tokens per session scan A 25e1dcd4f2c6
bp-learn is a skill published in the GitHub repository kulmam92/cc-best-practices-marketplace (2 stars, last pushed 5mo ago), licensed MIT. It adds 67 tokens to every session and 1,132 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.