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 EzraApple/skills-init --skill repo-automationsgit clone --depth 1 https://github.com/EzraApple/skills-initWrote 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/ezraapple/skills-init/repo-automations)<a href="https://agentmods.dev/skills/ezraapple/skills-init/repo-automations"><img src="https://agentmods.dev/badge/skills/ezraapple/skills-init/repo-automations/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/ezraapple/skills-init/repo-automations"><img src="https://agentmods.dev/badge/skills/ezraapple/skills-init/repo-automations.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.00354 |
| Opus 5.5 | $0.00013 | $0.00142 |
| Sonnet 5.5 | $0.00007 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
repo-automations 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 18d 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.
What it actually says
Repository automations
Find the existing playbook, code, workflow, and runtime before changing the automation. Establish which system owns the trigger, deployed revision, credentials, execution state, and delivery. Repository configuration alone cannot establish what actually ran.
Keep deterministic transformation and transport in code or workflow configuration. Use an agent playbook for work that needs investigation or judgment. Keep scheduling and runtime grants with their owning host. Preserve working conventions rather than introducing a new automation framework.
When the host can read the repository, its prompt should point to the playbook available in that runtime's checkout. Avoid a second copy of the procedure. Use ordinary Markdown for individual routines so each one does not become a separate discoverable skill. TEMPLATE.md is a starting point for new routines; omit fields that do not help.
For retries or external writes, define a stable deduplication key, the single owner of each write, and the state to read before retrying. A partial operation needs a recovery or compensation path. During migrations, prevent old and new writers from overlapping unless duplicate execution is safe. A playbook does not grant permission to send messages or make other external changes.
Check the real output and run record. For failures, isolate whether the trigger fired, the correct revision ran, access was available, the procedure selected the right data, and the destination accepted the result. Fix the owning layer; do not add prose to compensate for a scheduler or access problem.
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.
- 18d ago Changed · -21 lines · -50 tokens per session ac6b1b512b14
- 2mo ago First seen · 55 lines · 83 tokens per session scan A 558e3d260cae
repo-automations is a skill published in the GitHub repository EzraApple/skills-init (2 stars, last pushed 19d ago), licensed MIT. It adds 33 tokens to every session and 354 once invoked, about $0.0001 per session on Opus 5.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
oma-scholar
Search academic literature and generate, validate, or compare Knows paper sidecars. Use for claim/evidence analysis and literature synthesis.
pkf-writing
Author, update, convert, validate, persist, and render PKF (.pkf) content through message-inline, Library Asset, or Memory Page carriers. Use for structured reports, knowledge pages, delivery cards, or any .pkf body. NOT for recall, memory-graph placement, or curation decisions — those belong to the memory skill.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
render-3d-product-showcase
Assemble a premium 3D product-showcase ad from a config — four beat clips (an orbiting hero rotation, a macro push-in, a physics reveal, a typographic close) normalized to the chosen backdrop colour, hard-concatenated in order, closed on a deterministic Playwright brand end card, and mixed under one instrumental bed…
render-airdrop-carousel
Assemble a viral iOS "AirDrop" notification-carousel video ad (≈6–8s, 9:16) from a brand line plus 6–16 real product photos — a native AirDrop share-sheet card ("Brand would like to share a · Decline / Accept") springs up and its preview window CYCLES through the products, landing on a range/lineup payoff with an…
email-lifecycle-flow-writer
Step of the email-lifecycle playbook: writes one lifecycle flow as a build sheet for the brand's email tool, every message finished in the brand voice. Run email-lifecycle instead; not for direct use.