Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/fergupa/claude_pluginsnpx agentmods add commands/fergupa/claude_plugins/kb-articleWrote 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/commands/fergupa/claude_plugins/kb-article)<a href="https://agentmods.dev/commands/fergupa/claude_plugins/kb-article"><img src="https://agentmods.dev/badge/commands/fergupa/claude_plugins/kb-article/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/commands/fergupa/claude_plugins/kb-article"><img src="https://agentmods.dev/badge/commands/fergupa/claude_plugins/kb-article.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.00012 | $0.00699 |
| Opus 5.5 | $0.00005 | $0.00280 |
| Sonnet 5.5 | $0.00002 | $0.00140 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
kb-article 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 1mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KB Article
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Draft a publish-ready knowledge base article from a resolved support issue, common question, or documented workaround. Structures the content for searchability and self-service.
Usage
/kb-article <resolved issue, ticket reference, or topic description>
Examples:
/kb-article How to configure SSO with Okta — resolved this for 3 customers last month/kb-article Ticket #4521 — customer couldn't export data over 10k rows/kb-article Common question: how to set up webhook notifications/kb-article Known issue: dashboard charts not loading on Safari 16
Workflow
1. Understand the Source Material
Parse the input to identify:
- What was the problem? The original issue, question, or error
- What was the solution? The resolution, workaround, or answer
- Who does this affect? User type, plan level, or configuration
- How common is this? One-off or recurring issue
- What article type fits best? Use the article types from the knowledge-management skill (how-to, troubleshooting, FAQ, known issue, reference)
If a ticket reference is provided, look up the full context:
- ~~support platform: Pull the ticket thread, resolution, and any internal notes
- ~~knowledge base: Check if a similar article already exists (update vs. create new)
- ~~project tracker: Check if there's a related bug or feature request
2. Draft the Article
Using the article structure and formatting standards from the knowledge-management skill:
- Follow the template for the chosen article type (how-to, troubleshooting, FAQ, known issue, or reference)
- Apply the searchability best practices: customer-language title, plain-language opening sentence, exact error messages, common synonyms
- Keep it scannable: headers, numbered steps, short paragraphs
3. Generate the Article
Present the draft with metadata:
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.
- 1mo ago First seen · 84 lines · 12 tokens per session scan A fd0522e164a8
kb-article is a command published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 699 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.