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 ifiokjr/monopi --skill btwgit clone --depth 1 https://github.com/ifiokjr/monopiWrote 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/ifiokjr/monopi/btw)<a href="https://agentmods.dev/skills/ifiokjr/monopi/btw"><img src="https://agentmods.dev/badge/skills/ifiokjr/monopi/btw/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/ifiokjr/monopi/btw"><img src="https://agentmods.dev/badge/skills/ifiokjr/monopi/btw.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.00732 |
| Opus 5 | $0.00025 | $0.00366 |
| Sonnet 5 | $0.00010 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
btw 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BTW / QQ: side conversations
Use this skill when the user wants to work in parallel with the main agent instead of derailing the current turn.
Both /btw and /qq are identical. Use whichever feels natural. /qq stands for "quick question".
When to use BTW
Prefer the BTW workflow when the user wants to:
- ask a side question while the main agent keeps working
- brainstorm or compare options without interrupting the current run
- prepare a plan or summary before handing it back to the main agent
- keep exploratory discussion out of the main transcript/context
Commands
Use these commands in your guidance to the user:
/btw <question>
/btw --save <question>
/btw new [question]
/btw clear
/btw inject [instructions]
/btw summarize [instructions]
Every /btw command has a /qq equivalent:
/qq <question>
/qq --save <question>
/qq new [question]
/qq clear
/qq inject [instructions]
/qq summarize [instructions]
How to guide the user
For a quick side question
Recommend:
/btw <question>
or
/qq <question>
Use this when the user wants an immediate aside and does not need a visible saved note.
For a saved one-off note
Recommend:
/btw --save <question>
Use this when the user wants the exchange to appear as a visible BTW note in the session transcript.
For a fresh side thread
Recommend:
/btw new
or
/btw new <question>
Use this when the previous BTW discussion is no longer relevant.
To hand the full thread back to the main agent
Recommend:
/btw inject <instructions>
Use this when the exact discussion matters and the user wants the main agent to act on it.
To hand back a condensed version
Recommend:
/btw summarize <instructions>
Use this when the thread is long and only the distilled outcome should go back into the main agent.
Recommendation rules
- Prefer
/btwover normal chat when the user explicitly wants a side conversation. - Prefer
/btw summarizeover/btw injectfor long exploratory threads. - Prefer
/btw injectwhen precise wording, detailed tradeoffs, or a full plan matters. - Suggest
/btw newbefore starting a totally unrelated side topic. - Suggest
/btw clearwhen the widget/thread should be dismissed.
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 · 150 lines · 50 tokens per session scan A f3c9d1612169
btw is a skill published in the GitHub repository ifiokjr/monopi (150 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 732 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-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.