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 OutlineDriven/outline-driven-development --skill automate-megit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/automate-me)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/automate-me"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/automate-me.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00034 | $0.00917 |
| Opus 5 | $0.00017 | $0.00458 |
| Sonnet 5 | $0.00007 | $0.00183 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
automate-me 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 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- automate-me — 100% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automate me
Contract
| Field | Bound contract |
|---|---|
| Trigger | Create or refresh a personal mode skill. |
| Authority | Remote: pushes a branch and opens a reviewable PR; requires explicit human invocation. Previews the target file, skill content, and PR consequence before any write. |
| Side effect | Creates or edits one personal mode skill file in a local working copy on a new branch, commits it, pushes the branch, and opens a reviewable PR. No files beyond that skill file and no remote state beyond that branch and PR are touched; no credentials are read or written. |
| Done | Evidence-backed personal mode skill in a reviewable PR. |
Inputs
- A personal workflow to encode, supplied either as a direct description by the human or as a pointer to recent session or conversation history to mine for a repeated manual task pattern. At least one of these must be present.
- Target skill slug and file path. Optional; derive a slug from the workflow if the human does not supply one, and confirm it before writing.
- Repository and base branch to open the PR against. Must be supplied or determinable from the current working copy; if neither, stop and ask.
Procedure
- Require explicit human invocation. Confirm the human intends to author or refresh a personal mode skill and open a remote PR for it; do not proceed on inferred intent. Done when: the human confirms intent to author a personal skill and open a PR.
- Identify the recurring personal workflow. Use a description supplied by the human. Otherwise, mine recent session or conversation history for a task the human performs manually more than once. Name the repeated pattern and the sessions where it appears as evidence. Done when: the recurring workflow is named with supporting session evidence.
- If no recurring workflow can be supported by the history or description, stop and report that there is no candidate. Do not invent a workflow or fabricate history evidence. Done when: the absence of a candidate is reported or a candidate is confirmed.
- Draft the personal mode skill as a self-contained skill file with a name, trigger predicate, short procedure, and required inputs. The skill must not depend on another skill, module, or external rule file. Done when: the skill file is drafted as self-contained with all required sections.
- Show the human the target file path, full skill content, branch name, and consequence of opening a PR. Wait for explicit approval before any mutation. Done when: the human approves or declines the preview.
- On approval, create a new branch in the local working copy and create or edit the skill file at its target path. Write only that one file. Done when: the skill file is written on a new branch and no other file is touched.
- Commit the change with a message naming the personal workflow encoded. Done when: the commit is created with the workflow-naming message.
- Push the branch and open a reviewable PR whose description states the workflow encoded, the history evidence used, and the skill file path. Done when: the branch is pushed and the PR is opened with the required description.
- Capture the PR URL as the success evidence. Done when: the PR URL is captured.
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 Changed · -24 tokens per session bf2768ee1189
- 4d ago First seen · 45 lines · 58 tokens per session scan A 653934eebc84
automate-me is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 2d ago), licensed Apache-2.0. It adds 34 tokens to every session and 917 once invoked, about $0.0002 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-03.
Other skills, from other repositories
create-pull-request
Use when asked to create or update a PR, revise its description, or link issue references to its body. Not for multi-PR stacks: use gate-and-merge. Not for releases: use git-workflow-and-versioning.
commit-push-pr
Use when asked to commit, push a feature branch, and open or update a pull request with gh in one pass. Not for a push with no PR: use commit-push. Not for a PR body alone: use create-pull-request.
commit
Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push or commit-push-pr.
github-backlog-triage
Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.
git-branchless
Use when asked for multi-commit stack edits, rebases, fixups, or stacked-PR publishing with branchless git idioms. Not for plain-git workflows in repos without branchless.
setup-gitignore
Use when the user says set up gitignore, fix gitignore, or untracked files keep appearing. Not for remote, credential, publish, deploy, or irreversible changes.