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 causify-ai/helpers --skill skill.auto_addgit clone --depth 1 https://github.com/causify-ai/helpersWrote 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/causify-ai/helpers/skill.auto_add)<a href="https://agentmods.dev/skills/causify-ai/helpers/skill.auto_add"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/skill.auto_add/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/causify-ai/helpers/skill.auto_add"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/skill.auto_add.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00014 | $0.00870 |
| Opus 5.5 | $0.00006 | $0.00348 |
| Sonnet 5.5 | $0.00003 | $0.00174 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
skill.auto_add 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 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.
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
- The user gives you two arguments:
<FILE>: a path to a file that has been edited across one or more Git commits<PROMPT>: a path to a skill (SKILL.md) or prompt file to improve
- The edits to
<FILE>encode a lesson: someone had to fix something by hand that<PROMPT>should have gotten right the first time - Your job is to update
<PROMPT>so that, given the original<FILE>, it would now produce the final<FILE> - Generalize: infer the underlying rule, do not hard-code the specific strings from this one diff
Inputs
- If
<FILE>or<PROMPT>is missing or ambiguous, stop and ask the user rather than guessing - If
<FILE>has no committed changes, report that and stop
Workflow
Determine the Changes
- Find the commits that touched
<FILE>:> git log --oneline --follow -- <FILE> - Identify the first and last relevant revisions. Default to the full history of the file; if the user named a range, use that instead
- Extract
<CHANGES>as a unified diff:> git diff <FIRST_SHA> <LAST_SHA> -- <FILE>- If the diff is large, also read the final version in full so you
understand the intended end state, not just the deltas:
> git show <LAST_SHA>:<FILE>
- If the diff is large, also read the final version in full so you
understand the intended end state, not just the deltas:
- Do not use interactive commands (e.g.
git difftool): they block
Read the Prompt and the Conventions
- Read
<PROMPT>in full - Read
.claude/skills/skill.rules.mdfor the conventions and rules that govern how skills and prompts must be written - Read any files
<PROMPT>references, so you don't duplicate a rule that already lives elsewhere
Infer the Rules
- For each meaningful hunk in
<CHANGES>, write down:- what changed (before -> after)
- the general rule it implies
- whether
<PROMPT>already covers it (fully / partially / not at all)
- Drop hunks that are one-off content edits rather than repeatable rules (e.g. fixing a specific typo, updating a date): say explicitly which hunks you dropped and why
- Merge rules that are restatements of each other. Prefer one sharp rule over three overlapping ones
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 Changed b4fd69f89dc5
- 1mo ago Changed · +6 lines · -5 tokens per session f395cb43f1fc
- 1mo ago First seen · 91 lines · 19 tokens per session scan A 7428359eda17
skill.auto_add is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 870 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-09-03.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.