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 effect-ledgergit 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/effect-ledger)<a href="https://agentmods.dev/skills/jmagly/aiwg/effect-ledger"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/effect-ledger/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/jmagly/aiwg/effect-ledger"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/effect-ledger.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.00042 | $0.01261 |
| Opus 5.5 | $0.00017 | $0.00504 |
| Sonnet 5.5 | $0.00008 | $0.00252 |
| Haiku 4.5 | $0.00004 | $0.00126 |
Grade A, and why
effect-ledger 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 20d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Effect Ledger
Record and reconcile side effects (tracker comments, PR merges, issue closes,
git commits and tags, files, decision receipts) in the signed AIWG effect
ledger with the aiwg effect CLI. The ledger proves what AIWG recorded and
what a verifier observed. It never authorizes an effect and never replays one:
an operator decision authorizes, the ledger proves.
Triggers
- "record an effect" →
aiwg effect record - "sign an effect" →
aiwg effect record(signed intent and completed) - "reconcile effect" →
aiwg effect reconcile - "did this PR merge" →
aiwg effect reconcile --kind tracker.pr.merged, oraiwg effect probe --kind tracker.pr.merged --target gitea:owner/repo#34when no merge intent was recorded (read-only, writes nothing) - "did we already post this comment" →
aiwg effect lookupbefore posting - "verify the effect ledger" →
aiwg effect verify(add--with-decisions <audit.jsonl>to check #1567 operator-decision links) - "the effect ledger lock is stuck" →
aiwg effect recover-lock(operator only)
When to record
Record every externally visible effect that a retry or a crash could repeat: cycle and closing comments, merges, issue closes, tags, release files, and decision receipts. Do not record read-only queries.
Process
- Name the effect. Pick the kind and target, and the causal context that
makes it unique. For a cycle comment:
--kind tracker.comment --target gitea:owner/repo#12 --issue 12 --action cycle-comment --cycle 1.aiwg effect id <identity>prints the effect ID. - Check before acting. Run
aiwg effect lookup <identity>. Exit 0 means the effect is already present: do not repeat it. Exit 4 means an earlier attempt has no outcome: runaiwg effect reconcilefirst. - Carry the ID into the target wherever the target allows it: a hidden
<!-- aiwg-effect: <effect-id> -->line in a comment body, or anEffect-Id: <effect-id>git trailer. Verifiers use the marker to prove the effect happened. - Perform the effect, then record and sign it in one call:
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.
- 20d ago First seen · 99 lines · 42 tokens per session scan A 687997bf6b05
effect-ledger is a skill published in the GitHub repository jmagly/aiwg (224 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,261 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-09-26.
Other skills, from other repositories
launch
Planning releases and reporting delivery work from GitHub PR history. Use when versioning, CHANGELOGs, rollout or rollback plans, engineering metrics, retrospectives, or stakeholder reports are needed.
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy; the ship recipe also executes PR delivery (create, CI watch, merge, cleanup) with Ask First on merge. Use when PR preparation, commit strategy, or gated PR delivery is needed.
trail
Investigating git history, analyzing regression root causes, and performing code archaeology. Time-travels through commits to uncover truth. Use for git history investigation.
role-delivery
Use when the user assigns frontend, backend, backend-and-frontend, or review-only work and expects clear role boundaries, safe Git commits, or a copyable handoff to another agent.
missive
Invoke only when spawning a quest from a GitHub issue reference. Fetches GitHub issue context for quest spawning. Parses issue references, retrieves structured data via gh, and produces branch suggestions and PR keywords. Used standalone or as input to quest orchestration.
github
Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for issues, PRs, CI runs, and advanced queries.