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.00083 | $0.00663 |
| Opus 5 | $0.00042 | $0.00331 |
| Sonnet 5 | $0.00017 | $0.00133 |
| Haiku 4.5 | $0.00008 | $0.00066 |
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 11d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo automations
Use this skill as a router and ownership guide, not as a mandatory automation framework. Preserve the repository's established conventions unless they are the problem.
Orient
- Read the repository's agent guidance and automation documentation.
- Locate the actual automation surfaces: playbooks, scripts, workflow files, scheduler configuration, webhook handlers, and run records.
- If the request names an automation, find and read its playbook before acting. Search this directory and the repository rather than assuming a fixed layout.
- Confirm which system owns the trigger, checkout or deployed version, credentials, execution, and delivery. Do not infer runtime state from repository files alone.
Choose the owning layer
Use the smallest split that fits the existing system:
- Keep reviewable behavior, rules, and validation in the repository when practical.
- Keep timing, event bindings, runtime identity, and secret grants in the scheduler or automation host when that is where they naturally belong.
- Prefer code or workflow configuration for deterministic transformation and transport.
- Prefer an agent playbook when the work requires investigation, judgment, synthesis, or flexible tool use.
Do not migrate working provider-owned logic merely to conform to this pattern.
Route through playbooks
When a repository keeps automation playbooks beside this skill, use ordinary, frontmatter-free Markdown such as <slug>.md. This keeps the root skill discoverable without advertising every routine as an independent skill.
For a new repeated or consequential automation, start from TEMPLATE.md. Keep only the sections that improve execution; a short automation may need only a paragraph and a procedure.
Keep scheduler prompts thin when the host can read repository files: point to the playbook instead of duplicating its behavior. Add automation-specific trigger terms to this skill's description only when interactive discovery actually needs them.
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.
- 11d 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 1mo ago), licensed MIT. It adds 83 tokens to every session and 663 once invoked, about $0.0004 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
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
ijfw-writing-skills
Authoring discipline for new IJFW skills. Use when creating a new skill, writing a skill, making a skill that does X, or asked to add a skill. Trigger: create a new skill, write a skill, new skill, make me a skill, skill that does, /ijfw-writing-skills.