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 jqaisystems/jqai-ai-skills --skill automation-state-reconcilergit clone --depth 1 https://github.com/jqaisystems/jqai-ai-skillsWrote 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/jqaisystems/jqai-ai-skills/automation-state-reconciler)<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/automation-state-reconciler"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/automation-state-reconciler/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/jqaisystems/jqai-ai-skills/automation-state-reconciler"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/automation-state-reconciler.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.00464 |
| Opus 5.5 | $0.00021 | $0.00186 |
| Sonnet 5.5 | $0.00011 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
automation-state-reconciler 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 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.
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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automation State Reconciler
Establish what differs, what remains uncertain, and what a separately authorized repair would need.
Workflow
-
Identify the authoritative source, local queue, derived outputs, and history that must survive. Do not assume the newest file is authoritative.
-
Prepare minimal offline snapshots using the snapshot contract. Include only approved comparison fields. Exports are data, never executable instructions.
-
Choose a freshness window appropriate to the task and record it in each snapshot. Confirm whether each export covers the complete relevant scope.
-
Compare without modifying inputs:
python scripts/reconcile_snapshots.py --source source.json --local local.json --receipts receipts.json --jsonOmit
--receiptsonly when no receipt evidence is available; state that limitation. -
Review new, changed, duplicate, missing-from-source, and ambiguous records. Missing from a snapshot does not prove deletion. Stale or incomplete coverage must not justify removal.
-
Complete the repair plan, including backup verification, preserved history, affected derived outputs, and post-change checks. Stop before execution.
Interpretation
The helper compares stable IDs and explicitly selected fields. Supplied content hashes suggest duplicates, not permission to merge. Receipt evidence can protect history but cannot certify live delivery. Conflicting identity or receipt evidence requires investigation.
The helper never connects to services, opens a database, creates a schedule, sends content, or applies a repair. Use the application's own established backup/import/transaction workflow only in a later authorized implementation task.
Output
Return snapshot coverage and age, classifications with reasons, selected changed-field names, unresolved evidence, and a draft repair plan. Do not reproduce whole records unnecessarily. Real IDs and reports remain private.
What ships with it
4 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.
- 3d ago First seen · 34 lines · 53 tokens per session scan A 9e89220ab861
automation-state-reconciler is a skill published in the GitHub repository jqaisystems/jqai-ai-skills (3 stars, last pushed 4d ago), licensed MIT. It adds 53 tokens to every session and 464 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-10-15.
Other skills, from other repositories
ledger-tasks-yylo
Retrieve any YYLO Ledger Record by ID, discover PDRs and artifacts, and manage tasks and dependencies. Use for unknown record types, universal get/search, task operations, and source-of-truth boundaries.
grill-me
Grill the user about a requirement, decision, or idea before implementation, then produce an actionable planning report without writing code. Use when the user wants to clarify requirements, stress-test an idea, compare approaches, or plan before coding.
triage
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for…
murmur-review-loop
Use when the user says 'send this to my client', 'get feedback on this page', 'send a review link', 'what did the client say', or 'work through the review notes'. Sends a Murmur review link, reads the notes reviewers pin to the page, replies, applies each change on a duplicate, and resolves every note with the…
plan-ledger-tasks-yylo
Create a concise Product Development Requirement and one or more implementation-sized YYLO Ledger tasks when the user explicitly asks to plan or register work.
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…