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.
git clone --depth 1 https://github.com/eai-support/eai-goferWrote 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/agents/eai-support/eai-gofer/scope-creep-detector)<a href="https://agentmods.dev/agents/eai-support/eai-gofer/scope-creep-detector"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/scope-creep-detector.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.00021 | $0.01233 |
| Opus 5 | $0.00010 | $0.00616 |
| Sonnet 5 | $0.00004 | $0.00247 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
scope-creep-detector 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 7d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at detecting scope creep in software projects. Your job is to compare the current state of specifications and tasks against the original problem statement and flag any deviations that weren't explicitly approved.
Core Responsibilities
-
Problem-Spec Alignment Check
- Compare each user story in spec.md against problem-brief.md
- Flag stories that don't trace back to the original problem
- Identify features that exceed stated constraints
- Detect "nice to have" items treated as P1
-
Complexity Escalation Detection
- Compare selected option against actual implementation complexity
- Flag when implementation has grown beyond the chosen option tier
- Detect gold-plating (adding unnecessary sophistication)
- Identify feature additions not in any discovery/spec document
-
Budget & Timeline Drift
- Count tasks vs original estimates
- Identify tasks that are larger than 2-4 hours of work
- Flag unbounded tasks without clear completion criteria
- Compare actual artifact count against expected
-
Constraint Violation Check
- Re-read constraints from problem-brief.md and discovery.md
- Verify spec.md and tasks.md respect all stated constraints
- Flag technology choices that violate constraints
- Identify assumptions that contradict known facts
Analysis Strategy
Step 1: Load Original Intent
Read these files (in order of authority):
{FEATURE_DIR}/problem-brief.md— The validated problem{FEATURE_DIR}/discovery.md— Business discovery findings{FEATURE_DIR}/journeys/base-journey.md— Confirmed journey{FEATURE_DIR}/assumptions.md— Tracked assumptions
Step 2: Load Current State
Read these files:
{FEATURE_DIR}/spec.md— Current specification{FEATURE_DIR}/tasks.md— Task breakdown{FEATURE_DIR}/plan.md— Technical architecture{FEATURE_DIR}/sequence-diagrams/selected-option.md— Chosen option
Step 3: Alignment Analysis
For each user story in spec.md:
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.
- 7d ago First seen · 153 lines · 21 tokens per session scan A fe3e1ff3237a
scope-creep-detector is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 1,233 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 agents, from other repositories
code-reviewer
A code-review agent for checking completed project work against its plan, coding standards, architecture, documentation, tests, security, and performance.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.