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 leecyno1/boutique-skills --skill byterovergit clone --depth 1 https://github.com/leecyno1/boutique-skillsWrote 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/leecyno1/boutique-skills/byterover)<a href="https://agentmods.dev/skills/leecyno1/boutique-skills/byterover"><img src="https://agentmods.dev/badge/skills/leecyno1/boutique-skills/byterover/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/leecyno1/boutique-skills/byterover"><img src="https://agentmods.dev/badge/skills/leecyno1/boutique-skills/byterover.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.00057 | $0.00919 |
| Opus 5 | $0.00028 | $0.00460 |
| Sonnet 5 | $0.00011 | $0.00184 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
byterover 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 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.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ByteRover Context Tree
A project-level knowledge repository that persists across sessions. Use it to avoid re-discovering patterns, conventions, and decisions.
Why Use ByteRover
- Query before working: Get existing knowledge about patterns, conventions, and past decisions before implementing
- Curate after learning: Capture insights, decisions, and bug fixes so future sessions start informed
Quick Reference
| Command | When | Example |
|---|---|---|
brv query "question" |
Before starting work | brv query "How is auth implemented?" |
brv curate "context" -f file |
After completing work | brv curate "JWT 24h expiry" -f auth.ts |
brv status |
To check prerequisites | brv status |
When to Use
Query when you need to understand something:
- "How does X work in this codebase?"
- "What patterns exist for Y?"
- "Are there conventions for Z?"
Curate when you learned or created something valuable:
- Implemented a feature using specific patterns
- Fixed a bug and found root cause
- Made an architecture decision
Curate Quality
Context must be specific and actionable:
# Good - specific, explains where and why
brv curate "Auth uses JWT 24h expiry, tokens in httpOnly cookies" -f src/auth.ts
# Bad - too vague
brv curate "Fixed auth"
Note: Context argument must come before -f flags. Max 5 files.
Best Practices
-
Break down large contexts - Run multiple
brv curatecommands for complex topics rather than one massive context. Smaller chunks are easier to retrieve and update. -
Let ByteRover read files - Don't read files yourself before curating. Use
-fflags to let ByteRover read them directly:# Good - ByteRover reads the files brv curate "Auth implementation details" -f src/auth.ts -f src/middleware/jwt.ts # Wasteful - reading files twice # [agent reads files] then brv curate "..." -f same-files -
Be specific in queries - Queries block your workflow. Use precise questions to get faster, more relevant results:
# Good - specific brv query "What validation library is used for API request schemas?" # Bad - vague, slow brv query "How is validation done?"
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 95 lines · 57 tokens per session scan A 285f428fe69a
byterover is a skill published in the GitHub repository leecyno1/boutique-skills (5 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 919 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-09-03.
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.