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 jmagly/aiwg --skill git-mirror-auditgit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/jmagly/aiwg/git-mirror-audit)<a href="https://agentmods.dev/skills/jmagly/aiwg/git-mirror-audit"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/git-mirror-audit.svg" alt="Measured on agentmods" 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.00022 | $0.00498 |
| Opus 5 | $0.00011 | $0.00249 |
| Sonnet 5 | $0.00004 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
git-mirror-audit scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `.aiwg/security/curl-checklist-gap-analysis.md` row 3, Practice 21 What it actually says
Git Mirror Audit
Audit redundant git mirrors declared in .aiwg/aiwg.config:
{
"remotes": {
"primary": "origin",
"secondary": [
{
"name": "github",
"purpose": "backup-mirror",
"push_on_release": true
}
]
}
}
Execution Flow
- Read
remotes.primary,delivery.default_branch, andremotes.secondary[]. - Confirm every configured secondary exists in
git remote. - Fetch remote refs in read-only mode when the operator permits network access.
- Compare
refs/remotes/{primary}/{default_branch}with each secondary's default branch ref. - Report drift, missing remotes, and last known commit for each mirror.
Semantics
purpose: backup-mirrormeans the mirror is a disaster-recovery copy and should receive release pushes.push_on_release: truemeans release procedures must push tags and release commits to that mirror before declaring release complete.- This skill audits state; it never performs the push.
References
agentic/code/addons/aiwg-utils/rules/delivery-policy.md.aiwg/security/curl-checklist-gap-analysis.mdrow 3, Practice 21
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.
- 3d ago First seen · 65 lines · 22 tokens per session scan A 6fde42ad8c5b
git-mirror-audit is a skill published in the GitHub repository jmagly/aiwg (209 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 498 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
memstack-development-changelog-generator
Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.
release
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
autoship
Runs a changesets npm release through the version PR, CI publish, and registry verification. Use when asked to "release this package", "autoship", "merge Version Packages", or diagnose a release that did not publish. For feature PRs use pr-creator or pr-babysitter.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
source-command-update-infos-release
Update Codex releases tracking (guide + landing + version bump).
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.