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-developmentgit 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-development)<a href="https://agentmods.dev/skills/kdaip/echobot/echobot-development"><img src="https://agentmods.dev/badge/skills/kdaip/echobot/echobot-development/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-development"><img src="https://agentmods.dev/badge/skills/kdaip/echobot/echobot-development.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.00114 | $0.00915 |
| Opus 5.5 | $0.00046 | $0.00366 |
| Sonnet 5.5 | $0.00023 | $0.00183 |
| Haiku 4.5 | $0.00011 | $0.00092 |
Grade A, and why
echobot-development 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EchoBot Development
Work inside the current repository layout. Keep changes small, readable, and shared across CLI, gateway, and app entrypoints.
Start here
- Read
AGENTS.mdbefore non-trivial changes. - Keep Python 3.11+ code beginner-friendly. Prefer
pathlib. Keep one clear responsibility per function or class. - Do not block the event loop. Move blocking file, network, or CPU-heavy work to
asyncio.to_thread(...)or an executor. - Find the real entrypoint first:
echobot/cli/main.py,echobot/cli/chat.py,echobot/cli/gateway.py,echobot/cli/app.py, orechobot/app/create_app.py. - Reuse the shared runtime assembly in
echobot/runtime/bootstrap.py. If a feature should exist in chat, gateway, and app, wire it there once.
Choose the right layer
- Change
echobot/orchestration/decision.pyorechobot/orchestration/route_modes.pyfor route selection only. - Change
echobot/orchestration/roleplay.pyfor visible persona replies, delegated acknowledgements, and final presentation only. - Change
echobot/agent.py,echobot/runtime/session_runner.py, orechobot/runtime/turns.pyfor background agent behavior, tools, skills, memory, and scheduling. - Change
echobot/tools/orechobot/skill_support/instead of duplicating tool or skill wiring in one entrypoint. - Change
echobot/commands/andechobot/cli/session_commands.pyfor/route,/runtime,/role, and session command behavior. - Change
echobot/app/routers/,echobot/app/services/, andechobot/app/web/for HTTP or browser UI behavior.
Practical workflow
- Locate the entrypoint and the owning layer.
- Trace shared wiring through
build_runtime_context(...),ConversationCoordinator, andSessionAgentRunner. - Make the smallest coherent change.
- Add or update focused tests under
tests/. - Run the narrowest useful test group first, then expand if the change crosses subsystem boundaries.
Shared runtime rules
- Keep one source of truth for sessions, tools, skills, route modes, runtime settings, and scheduling.
- Extend
create_basic_tool_registry(...)or the tool-registry factory instead of hand-building tool lists for one surface. - Keep skill behavior inside
echobot/skill_support/and repository-local skills underskills/. - Preserve the separation between user-facing roleplay context and background agent execution context.
- Use
json.dumps(..., ensure_ascii=False)for JSON output. - When changing a project skill, validate it with
python -X utf8 echobot/skills/skill-creator/scripts/quick_validate.py skills/<skill-name>.
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 · 60 lines · 114 tokens per session scan A 83fa492c01ef
echobot-development is a skill published in the GitHub repository KdaiP/EchoBot (649 stars, last pushed 2mo ago), licensed MIT. It adds 114 tokens to every session and 915 once invoked, about $0.0005 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…