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 ALTEN-group/coding-pal --skill scope-guardgit clone --depth 1 https://github.com/ALTEN-group/coding-palWrote 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/alten-group/coding-pal/scope-guard)<a href="https://agentmods.dev/skills/alten-group/coding-pal/scope-guard"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/scope-guard/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/alten-group/coding-pal/scope-guard"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/scope-guard.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.00050 | $0.00528 |
| Opus 5.5 | $0.00020 | $0.00211 |
| Sonnet 5.5 | $0.00010 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
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 24d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope Guard
Deterministically enforce blast-radius bounds, forbidden path rules, and diff churn limits before committing changes or concluding an agent task.
When to Use This Skill
- An AI coding agent has completed a surgical change (e.g.
audit-fix,unit-test) and must verify no out-of-scope files or lockfiles were contaminated. - A workflow or harness hook needs to mechanically assert that git modifications remain bounded within a defined subfolder or module.
- CI/CD pipelines need a fast, deterministic check to reject PRs that exceed churn thresholds or touch protected files.
Path resolution
Resolve references/ and scripts/ relative to this skill's install directory (the folder containing this SKILL.md). In APM consumer projects, this typically resolves to .agents/skills/scope-guard/ or .claude/skills/scope-guard/.
Workflow
- Read
references/guard-contract.mdfor invariant definitions, forbidden file defaults, and exit codes. - After making code changes, run the deterministic validator:
# Check current git repository against authorized scopes
node scripts/scope-guard.mjs --git --scope "src/auth/**" --scope "tests/auth/**"
# Enforce churn thresholds (max lines added / deleted)
node scripts/scope-guard.mjs --git --scope "src/**" --max-additions 80 --max-deletions 40
# Check explicit files or inspect JSON diagnostics
node scripts/scope-guard.mjs --file "src/auth/service.js" --scope "src/auth/**" --json
- Treat a nonzero exit code as a scope violation. If forbidden files were touched or scope was breached:
- Revert unauthorized files:
git checkout -- <unauthorized-file>. - Remove newly created untracked files:
rm <unauthorized-file>. - Re-run the validator until it exits with code 0.
- Revert unauthorized files:
Done When
scripts/scope-guard.mjsexits with code 0.- All touched files reside strictly within the permitted
scopepatterns. - No forbidden files (
*.lock,*-lock.json,.env*) have been modified or created.
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.
- 24d ago First seen · 47 lines · 50 tokens per session scan A 3fe338c73152
scope-guard is a skill published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 528 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-09-24.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.