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/sammcj/agentic-coding/find-skillsnpx skills add sammcj/agentic-coding --skill find-skillsgit clone --depth 1 https://github.com/sammcj/agentic-codingWrote 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/sammcj/agentic-coding/find-skills)<a href="https://agentmods.dev/skills/sammcj/agentic-coding/find-skills"><img src="https://agentmods.dev/badge/skills/sammcj/agentic-coding/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.00074 | $0.02300 |
| Opus 5 | $0.00037 | $0.01150 |
| Sonnet 5 | $0.00015 | $0.00460 |
| Haiku 4.5 | $0.00007 | $0.00230 |
Grade E, and why
find-skills scanned grade E with 3 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 yesterday.
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.
Instruction-override phrasinghighPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
- Instructions to ignore previous instructions or override system prompts Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- `curl | bash`, `wget | sh`, `curl | sh`, or equivalent piped-execution patterns Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl | bash`, `wget | sh`, `curl | sh`, or equivalent piped-execution patterns How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Skills
This skill helps you search for and evaluate skills from the open agent skills ecosystem, then present your findings to the user so they can make an informed decision about installation.
Security Context
A skill is arbitrary code that runs with your (the agent's) full permissions. This includes filesystem access, network access, and the ability to execute commands. Treat skill discovery the same way you would treat evaluating a new dependency in a software project: search, assess, report findings, and let the human decide.
You must never install a skill without explicit user confirmation. You must never use flags that bypass confirmation prompts (e.g. -y, --yes). Your role is researcher and advisor, not installer.
When to Use This Skill
Use this skill when the user:
- Asks "how do I do X" where X might be a common task with an existing skill
- Says "find a skill for X" or "is there a skill for X"
- Wants to search for tools, templates, or workflows
- Mentions they wish they had help with a specific domain
Do NOT proactively suggest installing skills when the user simply asks for help with a task. Help them directly first. Only search for skills if the task is specialised enough that a dedicated skill would meaningfully outperform your general capabilities.
Skills CLI Reference
The Skills CLI (npx skills) is the package manager for the open agent skills ecosystem.
| Command | Purpose |
|---|---|
npx skills find [query] |
Search for skills by keyword |
npx skills add <package> |
Install a skill (user should run this themselves) |
npx skills check |
Check for updates to installed skills |
npx skills update |
Update installed skills |
Browse skills at: https://skills.sh/
Workflow
1. Clarify What the User Needs
Before searching, confirm:
- The domain (e.g. React, testing, infrastructure)
- The specific task (e.g. writing integration tests, reviewing PRs)
- Whether a skill is likely to add value beyond what you can already do
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.
- yesterday First seen · 228 lines · 74 tokens per session scan E 59602c151f4c
find-skills is a skill published in the GitHub repository sammcj/agentic-coding (159 stars, last pushed yesterday), licensed Apache-2.0. It adds 74 tokens to every session and 2,300 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it E with 3 findings (instruction-override phrasing, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
strands-review
Local preview of the strands-agents/devtools /strands review agent. Body is the upstream Task Reviewer SOP verbatim — do not paraphrase. Use when the user types /strands-review, asks for a "strands review" of a PR, or wants to anticipate what the remote /strands review GitHub Action will flag. Findings are close but…
pr-writer
Generates pull request titles and descriptions. Use when the user asks to create, open, write, draft, or generate a PR, pull request, or merge request description.
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
pre-push
Runs the local equivalent of the CI merge gate before you push. Detects which areas (Python, TypeScript, docs) your changes touch, auto-fixes what it can, then runs only those checks. Use when the user asks to run pre-push checks, get push-ready, verify changes before pushing or opening a PR, "make sure CI will pass"…
docs-planner
Identify documentation gaps and prioritize the docs backlog. Use when planning a docs improvement sprint, after signals surface repeated friction, when new SDK features ship without docs, or for periodic health assessment. Also triggers on "plan docs work", "what docs need writing", "prioritize the backlog", "docs…
pr-feedback
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.