scope-guard

A passive checker that compares the files changed in Git with the work plan and identifies changes outside the agreed scope. Git is the version-control system used to track those changes.

In plain words
What is it for?
Use it during a task to review the change summary, classify files as planned or unplanned, and flag minor or significant scope expansion.
Why use it?
It makes scope creep visible without blocking the developer, while recognising that tests, configuration, and lock files may be natural parts of a change.

Agent

Install

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.

agentmods
npx agentmods add agents/rune-kit/rune/scope-guard
Clone the repo
git clone --depth 1 https://github.com/Rune-kit/rune
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 246 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.00246
Opus 5 $0.00020 $0.00123
Sonnet 5 $0.00008 $0.00049
Haiku 4.5 $0.00004 $0.00025

Measured 2d ago against content hash 85a07e80a5d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

scope-guard 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 2d 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.

agents/scope-guard.md · 26 lines

What it actually says

You are the scope-guard skill — Rune's scope creep detector.

Quick Reference

Workflow:

  1. Load plan from TodoWrite or .rune/progress.md
  2. Run git diff --stat + git diff --cached to see actual changes
  3. Classify each file: IN_SCOPE (planned) vs OUT_OF_SCOPE (unplanned)
  4. Flag test files, config changes, lock files as natural dependencies (not creep)
  5. Classify: IN_SCOPE / MINOR CREEP (1-2 files) / SIGNIFICANT CREEP (3+ files)
  6. Report with recommendations

Critical Rules:

  • Compare against stated scope (not just file count)
  • Flag specific files with reasoning
  • Advisory only — allow user override (not authoritarian)

Read skills/scope-guard/SKILL.md for the full specification.

Changes

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.

  1. 2d ago First seen · 26 lines · 41 tokens per session scan A 85a07e80a5d7

Subscribe to this mod's changes

scope-guard is an agent published in the GitHub repository Rune-kit/rune (84 stars, last pushed 17d ago), licensed MIT. It adds 41 tokens to every session and 246 once invoked, about $0.0002 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-30.

Related

Other agents, from other repositories

polymath

Cross-disciplinary synthesis; spawns domain-specific subagents, synthesizes findings across domains, and produces integrated insights.

pjt222/agent-almanac · 25 tokens

insistir-reviewer

Cross-review agent for insistir multi-agent orchestration. Reviews another agent's implementation and sends structured findings to the lead. Read-only — cannot edit or write files. Can run verification commands (tests, typecheck, lint) via whitelisted Bash. Enforces quality without gatekeeping. Do NOT use directly …

JairoTorregrosa/jaiskills · 76 tokens

insistir-researcher

Research agent for insistir orchestration. Researches best practices, framework documentation, and codebase patterns. Read-only — cannot edit or write files. Do NOT use directly — spawned by insistir skill orchestration.

JairoTorregrosa/jaiskills · 50 tokens

insistir-learnings-researcher

Knowledge search agent for insistir multi-agent orchestration. Searches docs/solutions/ for past solutions relevant to a query using grep-first strategy with parallel keyword searches including synonyms. Read-only — cannot edit, write, or execute commands. Do NOT use directly — spawned by insistir skill orchestration.

JairoTorregrosa/jaiskills · 68 tokens

insistir-worker

Implementation agent for insistir multi-agent orchestration. Implements a task or applies review fixes, commits, reports to lead. Do NOT use directly — spawned by insistir skill orchestration.

JairoTorregrosa/jaiskills · 42 tokens

askit-quality-grader

Judges whether a skill triggers and behaves correctly by running it against its eval-set and grading the outputs. Use when delegating a behavioral evaluation - the opt-in LLM-judge role behind askit-evaluate's behavioral mode, distinct from the deterministic conformance core.

product-on-purpose/agent-skills-toolkit · 60 tokens