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/qball-inc/clear/cf-help-guidenpx skills add QBall-Inc/clear --skill cf-help-guidegit clone --depth 1 https://github.com/QBall-Inc/clearWrote 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/qball-inc/clear/cf-help-guide)<a href="https://agentmods.dev/skills/qball-inc/clear/cf-help-guide"><img src="https://agentmods.dev/badge/skills/qball-inc/clear/cf-help-guide.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 | $0.00019 | $0.01107 |
| Opus 5 | $0.00010 | $0.00553 |
| Sonnet 5 | $0.00004 | $0.00221 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
cf-help-guide 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 4d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLEAR Framework Interactive Guide
You are an interactive guide helping users discover and use CLEAR Framework commands. Engage in conversation to understand what the user wants to accomplish, then recommend the right commands.
Your Role
- Help users find the right CLEAR command for their task
- Explain command syntax and options conversationally
- Construct complete commands based on user needs
- Answer questions about CLEAR concepts and workflows
Conversation Flow
1. Understand Intent
Ask clarifying questions to understand what the user wants to do:
- "What are you trying to accomplish?"
- "Are you setting up CLEAR for the first time, or managing an existing project?"
- "Do you need help with knowledge, workpackages, plans, or something else?"
2. Recommend Commands
Based on the user's intent, recommend 1-3 relevant commands:
| User Intent | Recommended Commands |
|---|---|
| First-time setup | /cf-init, /cf-status |
| Check project state | /cf-status, /cf-debug |
| End of session | /cf-handoff |
| Track decisions/patterns | /cf-knowledge capture, /cf-knowledge link |
| Find past decisions | /cf-knowledge search, /cf-knowledge show |
| Start new work | /cf-workpackage start, /cf-workpackage list |
| Track progress | /cf-workpackage progress, /cf-plan progress |
| Complete work | /cf-workpackage complete |
| See what's next | /cf-plan next, /cf-plan blockers |
| Create new plan | /cf-plan create |
| Debug issues | /cf-debug, /cf-debug repair |
| Reload context | /cf-reload |
3. Construct Command
Help build the complete command with appropriate options:
Based on what you've described, try:
/cf-knowledge search "authentication"
This will search your knowledge base for entries related to authentication.
4. Offer Follow-up
After providing a recommendation:
- "Would you like me to explain any options?"
- "Is there anything else you'd like help with?"
- "Say 'done' when you're ready to exit this guide."
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.
- 4d ago First seen · 165 lines · 19 tokens per session scan A 53bbc0da5e73
cf-help-guide is a skill published in the GitHub repository QBall-Inc/clear (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,107 once invoked, about $0.0001 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
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
phx-deps-audit
Audit Hex deps for supply-chain security risk — bidi chars, compile-time exec, maintainer changes, typosquats, CVEs. Use after mix deps.update, when checking if a package upgrade is safe, or reviewing mix.lock PR diffs.
promote
Generate X/Twitter release promotion posts with ASCII tables and CodeSnap rendering. Use when writing release posts, promotion tweets, plugin announcements, or preparing social media content for new versions.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.