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 Eliyce/paqad-ai --skill rule-script-reconcilergit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/rule-script-reconciler)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/rule-script-reconciler"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/rule-script-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/eliyce/paqad-ai/rule-script-reconciler"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/rule-script-reconciler.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 23 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00018 | $0.01015 |
| Opus 5 | $0.00009 | $0.00508 |
| Sonnet 5 | $0.00004 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
rule-script-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 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Detects every form of rules-as-scripts drift and writes .paqad/scripts/rules/.cache/drift.json:
| Code | Meaning |
|---|---|
RS-RULE-ADDED |
A markdown bullet without a <!-- @rule --> marker, or a marked rule absent from the map — an ungated addition. |
RS-RULE-EDITED |
Marker present, but the text hash differs from the map entry. |
RS-RULE-REMOVED |
A map entry whose marker is gone from the markdown. |
RS-SCRIPT-STALE |
A rule was edited but its scripts were not regenerated. |
RS-FIXTURE-FAIL |
A registered script no longer passes its own fixtures. |
RS-CACHE-INVALID |
The findings report exists but its rule_files_hash no longer reconciles. |
Any code except RS-CACHE-INVALID blocks feature-development per the project's escalation.rule_scripts_stale setting.
Use This When
- At
feature-developmentplanning entry (the planning stage instructions invoke it). - During
analyze rules, to confirm the map is in sync before classifying.
Inputs
docs/instructions/rules/rule-script-map.yml(read-only).- The rule markdown under
docs/instructions/rules/**(read-only — no marker embedding here). - The registered
.paqad/scripts/rules/**/*.mjsscripts and their fixtures. - The cached
.paqad/scripts/rules/.cache/report.jsonfor the cache-validity check.
Procedure
- Run the reconciler:
Exit 0 = clean. Exit 1 = drift present (blocking).node scripts/reconcile.mjs [project-root] - Group findings by code. For each, surface a Decision Pause packet:
RS-RULE-ADDED→ "Unmarked rule detected — treat as a new rule (runanalyze rules) or as an edit of an existing rule?"RS-RULE-EDITED→ "Rule text changed —edit rule RL-…(regenerate scripts) or accept as-is?"RS-RULE-REMOVED→ "Marker gone —remove rule RL-…?"RS-SCRIPT-STALE/RS-FIXTURE-FAIL→ "Regenerate scripts forRL-…?"
- Apply the chosen resolution through
rule-editororrule-script-generator. Never edit the map directly.
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 · 79 lines · 18 tokens per session scan A f7807be1ba1e
rule-script-reconciler is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 1,015 once invoked, about $0.0001 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
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
auto-fix
A bug-fixing workflow that first reproduces a problem with a test, then applies the smallest code change needed. It also checks the related code path and runs tests afterward.
environment-diagnostics
Environment variable validation and configuration verification. Checks that required variables are set, config files parse correctly, ports are available, and system dependencies meet version requirements.
debugging
A structured method for finding and fixing software bugs. It starts by writing a test that reproduces the failure, then investigates its underlying cause before making a small fix.
ast-refactoring
A code-refactoring guide that uses an abstract syntax tree, a structured representation of source code, to make changes based on code meaning rather than text matching.
entropy-scan
A codebase health scan that measures disorder and highlights technical debt, meaning code problems that make future changes slower or riskier. It checks complexity, dependencies, repeated code, file size, and recent change frequency.