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 CiscoDevNet/essentials --skill essentials-syncgit clone --depth 1 https://github.com/CiscoDevNet/essentialsWrote 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/ciscodevnet/essentials/essentials-sync)<a href="https://agentmods.dev/skills/ciscodevnet/essentials/essentials-sync"><img src="https://agentmods.dev/badge/skills/ciscodevnet/essentials/essentials-sync.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.1 | $0.00101 | $0.01157 |
| Opus 5 | $0.00051 | $0.00579 |
| Sonnet 5 | $0.00020 | $0.00231 |
| Haiku 4.5 | $0.00010 | $0.00116 |
Grade A, and why
essentials-sync 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 2d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Essentials Sync
Driver for the essentials-sync CLI. The CLI does the work — extraction, scanning (TruffleHog, secretlint, jargon, PII), the adversarial review loop, and all writes. This skill only resolves the binary and holds the approval gate, because a real run writes to two working trees.
Agent workflow (required)
Run only scripts/run.sh. Do not invoke essentials-sync directly, do not hand-edit what it writes, and do not commit for the user.
1. Preflight
chmod +x scripts/run.sh
scripts/run.sh preflight
Stop and report if it fails. It checks Node >= 22, that the CLI resolves, and that CURSOR_API_KEY is set (or a .env is present for the CLI to load). A missing trufflehog is a warning, not a failure — that scanner is simply skipped.
2. Resolve the arguments
| Argument | Rule |
|---|---|
--source |
Absolute path. In default (extract) mode it must be a tools/python/<name>/ directory inside the source repo. Ask if the user did not give one. |
--target-repo |
Absolute path to the essentials clone. Must be a git working tree. Ask if missing. |
--target-path |
Relative to --target-repo. Optional in extract mode (defaults to packages/python/<package-name>), required with --no-extract. |
If the source is already generic and needs no extraction, add --no-extract — and then --target-path is mandatory.
3. Dry run
scripts/run.sh dry-run --source <abs> --target-repo <abs> [...]
The CLI stages everything into a temp directory instead of the real target.
4. GATE — wait for approval
Show the user the resolved command, the CLI's [plan], [source-scan], and [models] lines, and the dry-run outcome. Do not proceed until they explicitly approve.
5. Sync
scripts/run.sh sync --source <abs> --target-repo <abs> [...]
6. Report
State the exit code and run git status in both repos (the CLI prints the exact commands on success). Both trees are left dirty on purpose — the user reviews and commits.
What ships with it
2 files 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.
- 2d ago First seen · 99 lines · 101 tokens per session scan A ca4811646f87
essentials-sync is a skill published in the GitHub repository CiscoDevNet/essentials (7 stars, last pushed 18d ago), licensed Apache-2.0. It adds 101 tokens to every session and 1,157 once invoked, about $0.0005 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-09-04.
Other skills, from other repositories
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
triage-contributor-pr
Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
multiline-commit-messages
Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages.