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 KdaiP/EchoBot --skill echobot-skill-authoringgit clone --depth 1 https://github.com/KdaiP/EchoBotWrote 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/kdaip/echobot/echobot-skill-authoring)<a href="https://agentmods.dev/skills/kdaip/echobot/echobot-skill-authoring"><img src="https://agentmods.dev/badge/skills/kdaip/echobot/echobot-skill-authoring/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/kdaip/echobot/echobot-skill-authoring"><img src="https://agentmods.dev/badge/skills/kdaip/echobot/echobot-skill-authoring.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.00097 | $0.00907 |
| Opus 5.5 | $0.00039 | $0.00363 |
| Sonnet 5.5 | $0.00019 | $0.00181 |
| Haiku 4.5 | $0.00010 | $0.00091 |
Grade A, and why
echobot-skill-authoring 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EchoBot Skill Authoring
Create or revise repository-local skills that EchoBot can discover and activate.
Authoring goals
- Put project-specific skills under
skills/<skill-name>/. - Use lowercase kebab-case for the folder name and the
namefrontmatter field. - Keep frontmatter minimal. EchoBot routing reads
nameanddescriptionfromSKILL.md. - Keep
nameas a single-line value.descriptionmay be a single line or a YAML block scalar with>or|. - Write
descriptionas the trigger surface: what the skill does, when to use it, and what kinds of user requests or contexts should activate it. Include likely request phrasing when that improves triggering. - Keep the main body procedural and concise. Move deeper material into small files under
references/orscripts/. - Design for lazy loading. After activation, EchoBot exposes the body plus a resource summary. It does not auto-load bundled files.
- Only put text resources that an agent may need to read into
references/,scripts/, oragents/.read_skill_resourceonly reads UTF-8 text files. - Use
assets/for templates or binary output artifacts, not for essential instructions. - Do not treat
agents/openai.yamlas required. Current EchoBot discovery ignores it. - Avoid extra docs like
README.mdor changelog files inside a skill unless the runtime truly needs them.
Frontmatter checklist
- Keep
namestable and specific. Renaming a skill changes explicit/skill-nameand$skill-nameactivation. - Make
descriptionconcrete. Good descriptions say both the task and the trigger context. - Do not put "when to use" guidance only in the body. The body is loaded after activation.
- EchoBot currently ignores extra frontmatter keys. The validator is more permissive for compatibility, but project-local skills should usually keep only
nameanddescription.
Resource layout
skills/<skill-name>/
|-- SKILL.md
|-- references/ # short, focused UTF-8 docs loaded on demand
|-- scripts/ # executable helpers or deterministic workflows
|-- assets/ # templates or binary resources not meant for context loading
`-- agents/ # optional helper prompts or agent-specific text resources
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 64 lines · 97 tokens per session scan A 27df4e8201cc
echobot-skill-authoring is a skill published in the GitHub repository KdaiP/EchoBot (649 stars, last pushed 2mo ago), licensed MIT. It adds 97 tokens to every session and 907 once invoked, about $0.0004 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…