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/quantumbyteoss/quantumbyte/chat_formatting_widgetsnpx skills add QuantumByteOSS/quantumbyte --skill chat_formatting_widgetsgit clone --depth 1 https://github.com/QuantumByteOSS/quantumbyteWhat 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 | $0.00050 | $0.00186 |
| Opus 5 | $0.00025 | $0.00093 |
| Sonnet 5 | $0.00010 | $0.00037 |
| Haiku 4.5 | $0.00005 | $0.00019 |
Grade A, and why
chat-formatting-widgets 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 2d 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.
What it actually says
Chat Formatting & Markdown Widgets
Your chat replies render through the QB Markdown Renderer, which accepts ordinary markdown plus a small allow-list of inline HTML widgets. Anything outside this list is stripped or rendered literal.
Inline Highlight (Yellow Marker)
- Syntax:
<span class="highlight-mark">text</span> - Mandatory Rule: Wrap the core question phrase in
<span class="highlight-mark">...</span>whenever your message contains a question the user must answer (e.g. atomic child prompt, confirmation). - Limit: Highlight at most ONE phrase (3-8 words) per message. Do not highlight whole sentences.
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.
- 2d ago First seen · 14 lines · 50 tokens per session scan A b312819dae00
chat-formatting-widgets is a skill published in the GitHub repository QuantumByteOSS/quantumbyte (322 stars, last pushed 20d ago), licensed Apache-2.0. It adds 50 tokens to every session and 186 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
gsd
Get Shit Done (GSD) - A comprehensive project management system for solo developers using Claude agents.
st-full-workflow
Use when the user asks to run the complete end-to-end Strikethroo workflow for a work order in one shot in this repository — triggers include full workflow, end-to-end, plan and execute, do everything, run the whole strikethroo workflow. Do not use when the user wants only one stage (create a plan, generate tasks, or…
st-execute-blueprint
Use when the user asks to run, execute, implement, or carry out a Strikethroo plan or its blueprint by plan ID in this repository — triggers include execute blueprint, run the plan, implement plan, build the plan. Do not use to create a plan, to only generate tasks, to run a single task, or for generic development…
st-generate-tasks
Use when the user asks to decompose, break down, or generate tasks for an existing Strikethroo plan ID in this repository — triggers include generate tasks, break down the plan, decompose plan, create the task blueprint. Do not use to create a new plan, to execute tasks, or for generic project planning outside…
st-code-review
Use when the blueprint execution gate asks for an independent second-harness review of a Strikethroo plan's cumulative diff in this repository — triggers include code review gate, review the plan diff, second-model review, CODEREVIEW hook, review the cumulative diff. Do not use to review a single task, to review code…
st-execute-task
Use when the user asks to run, execute, or implement one specific task ID within a Strikethroo plan in this repository — triggers include execute task, run task, implement task, do task N. Do not use to execute a whole plan or blueprint, to generate tasks, or for generic development outside Strikethroo.