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/comisai/comis/find-skillsnpx skills add comisai/comis --skill find-skillsgit clone --depth 1 https://github.com/comisai/comisWrote 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/comisai/comis/find-skills)<a href="https://agentmods.dev/skills/comisai/comis/find-skills"><img src="https://agentmods.dev/badge/skills/comisai/comis/find-skills.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.00067 | $0.01105 |
| Opus 5 | $0.00034 | $0.00553 |
| Sonnet 5 | $0.00013 | $0.00221 |
| Haiku 4.5 | $0.00007 | $0.00111 |
Grade A, and why
find-skills 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 5d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Skills
Discover and install skills from the open agent skills ecosystem into Comis.
All script paths below are relative to this skill's directory. Resolve them against the directory containing the manifest file shown in <location>.
Invoke the resolved script by its absolute path while keeping the tool working directory inside the execution workspace. Never set cwd to the skill directory; it is outside workspace bounds. In command examples below, replace each relative scripts/... path with its resolved absolute path.
Workflow
Step 1: Distinguish installed state from catalog discovery
An installed-state request refers to the agent's current list or asks whether something is already
"installed", "available", or "in there". For an installed-state request, call skills_manage with
action: "list" first and answer only from that result. Do not run the public catalog search unless
the user separately asks to find an alternative.
A catalog result never proves that a skill is installed. Exit code 0 from npx skills find proves
only that the search completed and returned candidates. Never count a catalog candidate as installed,
describe it as newly installed, or call the current registry list stale.
Step 2: Understand what they need
Identify the domain (e.g., React, testing, deployment), the specific task (e.g., writing tests, reviewing PRs), and whether a skill likely exists for it.
Step 3: Search for skills
For an existing-skill discovery request, you must run npx skills find <query> first through exec
in the execution workspace. Use the non-interactive form:
Call exec directly for this catalog command. Do not call the find file tool: it searches
workspace filenames and cannot search the skills catalog. For an elliptical follow-up, derive
<query> from the concrete task named in the preceding user request; never search for the literal
follow-up wording.
npx --yes skills find <query>
Examples:
- User asks "how do I make my React app faster?" --
npx skills find react performance - User asks "can you help with PR reviews?" --
npx skills find pr review - User asks "I need to create a changelog" --
npx skills find changelog
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.
- 5d ago First seen · 106 lines · 67 tokens per session scan A 651d00162eb1
find-skills is a skill published in the GitHub repository comisai/comis (5 stars, last pushed today), licensed Apache-2.0. It adds 67 tokens to every session and 1,105 once invoked, about $0.0003 per session on Opus 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 skills, from other repositories
org-sync
Use when the CEO wants an organization-wide sync across PuPu's agent teams — running each org's internal sync, then a cross-org sync where departments challenge each other, converging into one decision list. Triggers: "跑一次 org sync", "全局同步", "组织盘点", "/org-sync", "各部门现在什么情况", "有什么要我拍板的".
release-feature-audit
Use when a new PuPu feature finishes implementation and needs its consistency audit before its ticket is marked done — "audit #123", "审计这个功能", "这个 feature 过一遍检查" — or when release-close-sprint roll-call finds a new feature that was never audited. Also covers standalone i18n checks ("漏翻了吗", "检查 i18n"), which used to be…
growth-analyst
Use when analyzing PuPu's open-source growth or health for the founder — GitHub traffic, downloads/installs, releases, community, or contributor activity — or when producing a growth report or weekly COO report. Repo is haoxiang-xu/PuPu. Triggers: "how is PuPu growing?", "are people installing PuPu?", "which release…
test-api
Use when running QA / regression tests against PuPu, when verifying a code change actually works in the running app, or when reading PuPu UI/state without screenshotting manually. Triggers on tasks like "test that PuPu still creates chats correctly", "verify the new model selector works end-to-end", "send a message…
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?".