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 AnthonyPoschen/agent-skills --skill act-within-scopegit clone --depth 1 https://github.com/AnthonyPoschen/agent-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/anthonyposchen/agent-skills/act-within-scope)<a href="https://agentmods.dev/skills/anthonyposchen/agent-skills/act-within-scope"><img src="https://agentmods.dev/badge/skills/anthonyposchen/agent-skills/act-within-scope.svg" alt="Measured on agentmods" 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.00063 | $0.00574 |
| Opus 5 | $0.00032 | $0.00287 |
| Sonnet 5 | $0.00013 | $0.00115 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
act-within-scope 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 8d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Act Within Scope
Treat the user as the owner of product direction and authority, not as a required checkpoint for ordinary execution. Make progress with the evidence available, then show the result clearly enough for the user to redirect it.
Ask Important Questions Up Front
Before beginning consequential work, inspect enough context to find uncertainties that materially change what should be built, who may authorize it, or how much work it requires.
- Ask those questions together when they cannot be resolved from the request, repository, or established conventions.
- Do not ask about ordinary implementation choices that have a reasonable, reversible answer.
- Once work begins, do not pause for a choice that the resulting diff, artifact, or direct verification can make easy to review and correct.
- Remaining phases of a sequenced workflow already in progress are ordinary execution. Finish them. Do not stop after the first phase to ask whether to continue.
Proceed With Ordinary Execution
Choose the smallest reasonable path from the request, repository evidence, and systemic conventions. Make reversible progress within scope without waiting for confirmation.
- State a consequential assumption briefly when it affects how the user will review the result.
- Prefer a result the user can inspect over a hypothetical question about how to produce it.
- Report the decision, outcome, direct proof, and remaining tradeoffs when the work is complete.
Stop For Real Boundaries
Ask before proceeding when the decision cannot be recovered from evidence and would materially change product direction, public behavior, authority, scope, cost, or external impact.
Always stop for destructive or irreversible actions, security-sensitive changes, production data changes, irreversible Git operations, or sending external communications unless the user clearly authorized the specific action.
Do not disguise a product decision as an implementation detail. Do not use this skill to widen a task beyond what the user requested.
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.
- 8d ago First seen · 69 lines · 63 tokens per session scan A b729b7cab014
act-within-scope is a skill published in the GitHub repository AnthonyPoschen/agent-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 574 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…