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/seifbenayed/cloclo/product-self-knowledgenpx skills add SeifBenayed/cloclo --skill product-self-knowledgegit clone --depth 1 https://github.com/SeifBenayed/clocloWrote 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/seifbenayed/cloclo/product-self-knowledge)<a href="https://agentmods.dev/skills/seifbenayed/cloclo/product-self-knowledge"><img src="https://agentmods.dev/badge/skills/seifbenayed/cloclo/product-self-knowledge.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.00138 | $0.00604 |
| Opus 5 | $0.00069 | $0.00302 |
| Sonnet 5 | $0.00028 | $0.00121 |
| Haiku 4.5 | $0.00014 | $0.00060 |
Grade A, and why
product-self-knowledge 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.
This is a copy
94% identical to product-self-knowledge — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Anthropic Product Knowledge
Core Principles
- Accuracy over guessing - Check official docs when uncertain
- Distinguish products - Claude.ai, Claude Code, and Claude API are separate products
- Source everything - Always include official documentation URLs
- Right resource first - Use the correct docs for each product (see routing below)
Question Routing
Claude API or Claude Code questions?
→ Check the docs maps first, then navigate to specific pages:
- Claude API & General: https://docs.claude.com/en/docs_site_map.md
- Claude Code: https://docs.anthropic.com/en/docs/claude-code/claude_code_docs_map.md
Claude.ai questions?
→ Browse the support page:
- Claude.ai Help Center: https://support.claude.com
Response Workflow
- Identify the product - API, Claude Code, or Claude.ai?
- Use the right resource - Docs maps for API/Code, support page for Claude.ai
- Verify details - Navigate to specific documentation pages
- Provide answer - Include source link and specify which product
- If uncertain - Direct user to relevant docs: "For the most current information, see [URL]"
Quick Reference
Claude API:
- Documentation: https://docs.claude.com/en/api/overview
- Docs Map: https://docs.claude.com/en/docs_site_map.md
Claude Code:
- Documentation: https://docs.claude.com/en/docs/claude-code/overview
- Docs Map: https://docs.anthropic.com/en/docs/claude-code/claude_code_docs_map.md
- npm Package: https://www.npmjs.com/package/@anthropic-ai/claude-code
Claude.ai:
- Support Center: https://support.claude.com
- Getting Help: https://support.claude.com/en/articles/9015913-how-to-get-support
Other:
- Product News: https://www.anthropic.com/news
- Enterprise Sales: https://www.anthropic.com/contact-sales
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 · 66 lines · 138 tokens per session scan A 216f66560c9f
product-self-knowledge is a skill published in the GitHub repository SeifBenayed/cloclo (114 stars, last pushed 5mo ago), licensed MIT. It adds 138 tokens to every session and 604 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to product-self-knowledge, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…