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 SummerSec/SumSec-Skills --skill rules-installergit clone --depth 1 https://github.com/SummerSec/SumSec-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/summersec/sumsec-skills/rules-installer)<a href="https://agentmods.dev/skills/summersec/sumsec-skills/rules-installer"><img src="https://agentmods.dev/badge/skills/summersec/sumsec-skills/rules-installer/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/summersec/sumsec-skills/rules-installer"><img src="https://agentmods.dev/badge/skills/summersec/sumsec-skills/rules-installer.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.00034 | $0.00443 |
| Opus 5.5 | $0.00014 | $0.00177 |
| Sonnet 5.5 | $0.00007 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
rules-installer 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 1mo 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.
What it actually says
Rules Installer
Install Semantic-Linter into the user's current project by generating two artifacts:
semantic-rules.md: the full semantic guidance file- a managed block in
AGENTS.mdand orCLAUDE.md: the lightweight always-present pointer
What This Skill Must Do
- Detect the current project directory with
pwd. - Locate
scripts/build-rules.jsfrom the active plugin or local source checkout. - Run:
node "<SCRIPT>" --existing "$(pwd)"
- Run:
node "<SCRIPT>" --check --existing "$(pwd)"
- Tell the user:
- which files were written
- whether validation passed
- that the default mode is
guarded - that project-local
semantic-rules.mdis preferred over the plugin fallback
Important Rules
- Never hand-write
semantic-rules.md. - Never hand-write the managed
<!-- STL:RULES:BEGIN -->block. - If both
AGENTS.mdandCLAUDE.mdalready exist, update both. - If neither file exists, let
build-rules.jscreate the host-appropriate default target.
Runtime Model
Semantic-Linter is no longer pointer-only.
- Claude can use
SessionStart,SubagentStart,UserPromptSubmit,PreToolUse, andPostToolUse. - Codex relies on the managed project instruction file and on-demand rule loading.
pointermode keeps only the lightweight pointer.guardedmode adds write-time lint checks.strictmode also enables prompt scanning.
When To Suggest Follow-up Commands
/stl-rulesafter policy or lexicon changes/stl-lexiconwhen the user wants to add or refine trap pairsnpm run scan -- <file>when the user wants an explicit one-off scan
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.
- 1mo ago First seen · 57 lines · 34 tokens per session scan A 13964fefd39b
rules-installer is a skill published in the GitHub repository SummerSec/SumSec-Skills (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 443 once invoked, about $0.0001 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-03.
Other skills, from other repositories
audit-playbook
A code-security audit playbook covering source-code review, runtime checks, software dependencies, deployment settings, and AI-agent security risks.
x64dbg-reversing
Perform dynamic reverse engineering and debugging using X64dbg/X32dbg through natural language commands powered by X64dbg MCP. Use this skill whenever the user wants to: debug executables, analyze program behavior at runtime, set breakpoints, inspect memory and registers, trace execution flow, bypass anti-debug…
novel-reviewer
A review and editing workflow for existing novel chapters. It checks story logic, timelines, character states, unresolved clues, world rules, and writing style.
ida-reversing
Perform reverse engineering and binary analysis in IDA Pro using natural language commands powered by IDA MCP. Use this skill whenever the user wants to: analyze executable files, understand function behavior, decompile code, explore cross-references, search for strings or bytes, patch binary code, document reverse…
video-recap
A workflow that turns a supplied video into a Chinese narrated recap by combining video understanding, story planning, editing, voiceover, and final assembly.
workflow-manager
A writing workflow tracker for chapter-based projects. It records whether each chapter is being assembled, drafted, reviewed, confirmed, polished, or archived.