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 mattbaconz/signal --skill signal-pushgit clone --depth 1 https://github.com/mattbaconz/signalWrote 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/mattbaconz/signal/signal-push)<a href="https://agentmods.dev/skills/mattbaconz/signal/signal-push"><img src="https://agentmods.dev/badge/skills/mattbaconz/signal/signal-push/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/mattbaconz/signal/signal-push"><img src="https://agentmods.dev/badge/skills/mattbaconz/signal/signal-push.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.00063 | $0.00942 |
| Opus 5 | $0.00032 | $0.00471 |
| Sonnet 5 | $0.00013 | $0.00188 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
signal-push 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚡ signal-push — Commit + Push
One command. Stages, commits, pushes. Done.
Invocation Triggers
Activate when user says any of:
/signal-push"commit and push","push everything","push my changes""push this","ship it","send to remote"/signal-commit --push
Slash command behavior
If the user's message is only /signal-push (optionally with flags like
--dry, --draft, or --split), treat that as execute now.
- Do not stop after acknowledging the skill.
- Do not ask for confirmation unless the user explicitly requested review mode.
- Immediately run the ordered steps below in the same turn.
- Respect
--dryand--draftexactly as defined in this file.
Behavior (Ordered Steps)
-
Run signal-commit logic — full diff analysis, message generation, staging, committing. See
signal-commit/SKILL.mdfor complete commit behavior. -
Push to remote
git pushIf no upstream is set (new branch), auto-set it:
git push --set-upstream origin {current-branch}No prompt. No confirmation. It pushes.
-
Report
✓ feat(auth): add JWT refresh token rotation [3 files, +47/-12] ✓ pushed → origin/feat/jwt-refresh
Flags
All flags from signal-commit are inherited, plus:
| Flag | Behavior |
|---|---|
--draft |
Show generated commit message, do not commit or push. |
--dry |
Explain what would happen — touch nothing. |
--split |
Force atomic commits per logical change, then push all. |
--dry output:
Would stage: 3 files
Would commit: feat(auth): add JWT refresh token rotation
Would push → origin/feat/jwt-refresh
Output Format
Single commit + push:
✓ feat(auth): add JWT refresh token rotation [3 files, +47/-12]
✓ pushed → origin/feat/jwt-refresh
Split commits + push:
✓ fix(api): handle null response from upstream [2 files, +8/-3]
✓ chore(deps): update axios to 1.6.2 [1 file, +2/-2]
✓ pushed → origin/main
What ships with it
3 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 · 128 lines · 63 tokens per session scan A 5245455155b4
signal-push is a skill published in the GitHub repository mattbaconz/signal (10 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 942 once invoked, about $0.0003 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
commit-staged
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
lov-checkpoint-list
A read-only history report built from Git records and project checkpoint logs. A checkpoint is a recorded project milestone or state, while Git is the version-control system that tracks changes and commits.
lov-git-commit-with-context
A Git commit helper that compares the current conversation's intended work with the repository's actual changes before creating a commit. Git is a system for tracking file changes, and a commit records a selected set of those changes.
chinese-commit-conventions
A Chinese-language convention for writing Git commit messages, based on Conventional Commits, a standard format that tools can use to classify changes and build changelogs.
atomic-commits
Commit discipline for every repository — small atomic commits, Conventional Commits messages, only commit working states. Use whenever creating git commits, splitting work into commits, or writing commit messages, in any project.
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…