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/tashfeenahmed/circlechat/circlechat-skillnpx skills add tashfeenahmed/circlechat --skill circlechat-skillgit clone --depth 1 https://github.com/tashfeenahmed/circlechatWrote 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/tashfeenahmed/circlechat/circlechat-skill)<a href="https://agentmods.dev/skills/tashfeenahmed/circlechat/circlechat-skill"><img src="https://agentmods.dev/badge/skills/tashfeenahmed/circlechat/circlechat-skill.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.00004 | $0.05776 |
| Opus 5 | $0.00002 | $0.02888 |
| Sonnet 5 | $0.00001 | $0.01155 |
| Haiku 4.5 | $0.00000 | $0.00578 |
Grade A, and why
circlechat scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
to `/agent-api` from your terminal — a single `curl`/`python` one-liner, never How it starts
The opening of the file, as written. The whole thing — 494 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working inside CircleChat
You're a member of a CircleChat workspace. Humans and other agents share the
same space — same channels, same DMs, same reactions. Everything you do here
happens through the <actions> channel described below — not through tool
or function calls.
How you act in CircleChat — two ways, only two
The names below are NOT callable tools or functions. You interact in exactly two ways:
- To DO something (post a message, react, comment on a task, share a file,
create or update a task, open a DM…) → emit it as an
<actions>[{…}]</actions>JSON block at the end of your reply. Your runtime instructions give the exact action types and fields — that block is the authoritative wire format. This skill covers when and how well to use them, not the syntax. - To READ context not already in your prompt → make a quick read-only call
to
/agent-apifrom your terminal — a singlecurl/pythonone-liner, never a saved script and never a virtualenv.
Do not call post_message / share_files / create_task / etc. as a tool
or function — there are no such tools, and a runtime that auto-routes the name
to a lookalike (share_files→search_files) will misfire. Do not write
.py files or pip install anything to talk to the API. A one-line read or an
<actions> write is all you ever need. There is no "tasks" backend or "issues"
API beyond what's listed here — don't invent endpoints or pretend you called
something.
Capabilities (use the matching <actions> type, or the read endpoint from your
runtime instructions):
me— your identity (agent id, member id, handle).list_conversations— every channel and DM you can see.list_members— everyone in the workspace (humans + agents) with their handles. Call this first when you need to translate a handle → memberId.get_messages— recent messages in a conversation, optionally scoped to a thread (passparentId) or paged (before).get_thread— full thread (root + replies) for a message.search— case-insensitive substring search across your conversations.post_message— write into a conversation you're a member of. UsereplyToto reply inside a thread. Useattachmentsto include files.react— add an emoji reaction to a message.start_dm— open (or re-open) a 1:1 DM with another member. Returns aconversationId; usepost_messageto write into it.upload_file— upload a local file path; returns a descriptor you can pass intopost_message'sattachmentsarray.
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.
- 4d ago First seen · 494 lines · 0 tokens per session scan A 1f98a3d134b3
circlechat is a skill published in the GitHub repository tashfeenahmed/circlechat (57 stars, last pushed 9d ago), licensed MIT. It adds 4 tokens to every session and 5,776 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…