Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/pjt222/agent-almanacnpx agentmods add skills/pjt222/agent-almanac/create-skillWrote 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/pjt222/agent-almanac/create-skill)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/create-skill"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/create-skill/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/pjt222/agent-almanac/create-skill"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/create-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 324 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 341 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00095 | $0.04481 |
| Opus 5.5 | $0.00038 | $0.01792 |
| Sonnet 5.5 | $0.00019 | $0.00896 |
| Haiku 4.5 | $0.00010 | $0.00448 |
Grade B, and why
create-skill scanned grade B 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 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
**Got:** `ls -la .claude/skills/<skill-name>/SKILL.md` resolves to the skill file. How it starts
The opening of the file, as written. The whole thing — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a New Skill
Author a SKILL.md file that agentic systems can consume to execute a specific procedure.
When to Use
- Codifying a repeatable procedure that agents should follow
- Adding a new capability to the skills library
- Converting a guide, runbook, or checklist into agent-consumable format
- Standardizing a workflow across projects or teams
Inputs
- Required: Task the skill should accomplish
- Required: Domain classification — one of the 48 domains in
skills/_registry.yml:r-packages,jigsawr,containerization,reporting,compliance,mcp-integration,web-dev,git,general,citations,data-serialization,review,bushcraft,esoteric,design,defensive,project-management,devops,observability,mlops,workflow-visualization,swarm,morphic,alchemy,tcg,intellectual-property,gardening,shiny,animal-training,mycology,prospecting,crafting,library-science,travel,relocation,a2a-protocol,geometry,number-theory,stochastic-processes,theoretical-science,diffusion,hildegard,maintenance,blender,visualization,3d-printing,lapidary,versioning - Required: Complexity level (basic, intermediate, advanced)
- Optional: Source material (existing guide, runbook, or working example)
- Optional: Related skills to cross-reference
Procedure
Step 1: Create Directory
Each skill lives in its own directory:
mkdir -p skills/<skill-name>/
Naming conventions:
- Use lowercase kebab-case:
submit-to-cran, notSubmitToCRAN - Start with a verb:
create-,setup-,write-,deploy-,configure- - Be specific:
create-r-dockerfilenotcreate-dockerfile
Got: Directory skills/<skill-name>/ exists, and the name follows lowercase kebab-case starting with a verb.
If fail: If the name does not start with a verb, rename the directory. Check for naming conflicts: ls skills/ | grep <keyword> to ensure no existing skill has an overlapping name.
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 · 419 lines · 95 tokens per session scan B 484b3b6281cc
create-skill is a skill published in the GitHub repository pjt222/agent-almanac (42 stars, last pushed 5d ago), licensed MIT. It adds 95 tokens to every session and 4,481 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
execute-phase
Step executor for units whose triage (unit-lane) decided which steps the unit needs. Implements one triaged step (or all remaining steps), with frozen acceptance, step-local gates, commits, red-gate repair, and diff-size guard. BREAKING: replaced PLAN.md/TASKS.md/progress.md/ACCEPTANCE.md with the unit doc's Tasks…
fold-findings
Repair persisted fix-now findings in compatible atomic batches: root-cause fixes, green gate, commit/push, and per-row folded: yes updates. Never reclassify or substitute backlog notes. Triggers: "fold-findings", "fix the review findings", "repair audit blockers".
init-workspace
Adapt the workflow scaffold to a new repository or add only missing substrate blocks to an existing install. Every install, hook, and overwrite needs explicit consent. Triggers: "init-workspace", "set up agentic workflow", "upgrade workflow scaffold".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling; it owns the repo-wide bug hunt, security research, and broken-version investigation (scoped and budgeted per dimension, as distinct from review-change's change-scoped review). Persist one severity-ranked, F-numbered report with…
review-change
Review a change with only applicable internal axes, classify every finding, persist fix-now work, and return one evidence-backed decision. Findings only; --adversarial N uses isolated reviewers; --synthesize fuses supplied reviewer tables. Triggers: "review-change", "review this change", "adversarial review".