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-editorgit 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-editor)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/rule-editor"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/rule-editor/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-editor"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/rule-editor.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 26 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.00017 | $0.01035 |
| Opus 5 | $0.00009 | $0.00517 |
| Sonnet 5 | $0.00003 | $0.00207 |
| Haiku 4.5 | $0.00002 | $0.00103 |
Grade A, and why
rule-editor 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 10d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Owns the mutation cascade so adding, editing, or removing a rule recomputes only what changed — never a full regeneration:
| Mode | Effect |
|---|---|
| add | Inserts the bullet into the target rule file, mints a stable RL-<hash> id, then classifies + generates scripts for only the new rule. |
| edit | Updates the bullet text, preserves the id, regenerates only that rule's scripts, and surfaces a behavior diff via Decision Pause when scripts change. |
| remove | Removes the bullet, moves the map entry to archived: (delayed delete); scripts pruned on the next regen pass. |
| downgrade | Keeps the rule, deletes its scripts, flips the map entry to verifiability.kind: unverifiable with a recorded reason. |
Use This When
- A user prompt matches the priority-225 router rules
add rule,edit rule,remove rule, ormark rule as unverifiable.
Inputs
- The target rule file (for
add) or theRL-<id>(for edit/remove/downgrade). - The new rule text (
add,edit) or downgrade reason (downgrade). docs/instructions/rules/rule-script-map.yml(written only via the bundled wrapper →src/rule-scripts/apply.ts).
Procedure
- Apply the deterministic mechanics:
node scripts/edit-rule.mjs add <project-root> <source-rel> "<text>" node scripts/edit-rule.mjs edit <project-root> RL-<id> "<text>" node scripts/edit-rule.mjs remove <project-root> RL-<id> node scripts/edit-rule.mjs downgrade <project-root> RL-<id> "<reason>" - For
addandedit: re-runanalyze rules(idempotent — touches only the changed rule) thengenerate rule scriptswithonly_rule_idset to the affected id, so only that rule's scripts are regenerated. - For
edit, diff the regenerated scripts against the prior ones; if behavior changed, surface a Decision Pause packet before accepting. - Present a
## Rule Change Summarynaming the id, the mode, and any scripts added/removed.
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.
- 10d ago First seen · 76 lines · 17 tokens per session scan A 81a5999e453c
rule-editor is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 1,035 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
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
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-go
A command that implements code from a SPEC, a document describing the required behavior and work.
auto-plan
A code-planning skill that examines a codebase and creates a detailed specification, implementation plan, and acceptance criteria. It can organize requirements using EARS, a structured way to describe how software should behave in different situations.
agent-pipeline
Multi-agent pipeline orchestration skill.
adaptive-quality
Per-task execution profile selection based on complexity in Balanced quality mode.