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 ronaknnathani/relay --skill commitgit clone --depth 1 https://github.com/ronaknnathani/relayWrote 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/ronaknnathani/relay/commit)<a href="https://agentmods.dev/skills/ronaknnathani/relay/commit"><img src="https://agentmods.dev/badge/skills/ronaknnathani/relay/commit/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/ronaknnathani/relay/commit"><img src="https://agentmods.dev/badge/skills/ronaknnathani/relay/commit.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.00053 | $0.00341 |
| Opus 5.5 | $0.00021 | $0.00136 |
| Sonnet 5.5 | $0.00011 | $0.00068 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
commit 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.
What it actually says
Commit
Create a single git commit for the current changes.
Gather context
First inspect the working tree. Run these read-only commands and read their output:
git status— what is staged and unstagedgit diff HEAD— the full staged and unstaged diffgit branch --show-current— the current branchgit log --oneline -10— recent commit message style to match
Create the commit
Based on the changes above, create one commit:
-
Stage the relevant files with
git add <specific-files>(stage the files this change touches, not unrelated work). -
Read
<repo>/AGENTS.mdand~/.config/agents/AGENTS.mdif present, then write a clear, concise commit message that matches those preferences and the repository's existing style. Lead with what changed and why. -
End the commit message with a
Co-authored-bytrailer for the actual model/agent currently doing the work. Use the runtime-provided model identity when available, and the agent's verified no-reply identity for the email. Never hardcode a model name. -
Commit with
git commit.
Use only git add, git status, and git commit. Do not push, do not run other tools, and do not take any other action.
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 · 30 lines · 53 tokens per session scan A 3a218d073369
commit is a skill published in the GitHub repository ronaknnathani/relay (3 stars, last pushed 23d ago), licensed MIT. It adds 53 tokens to every session and 341 once invoked, about $0.0002 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
conventional-commit
Generer conventional commit-meldinger med Nav-relevante scopes og breaking change-format.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
commit-with-reflection
A Git workflow that creates a Chinese-language report about debugging mistakes, investigation steps, fixes, and lessons learned, then includes that report in a commit. Git is a system for tracking changes to code.
antfu-create-pr
Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.