Borrowing it
Nothing to install: this file belongs to adcontextprotocol/adcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adcontextprotocol/adcp/main/.claude/agents/internal-tools-strategist.mdgit clone --depth 1 https://github.com/adcontextprotocol/adcpWrote 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/adcontextprotocol/adcp/internal-tools-strategist)<a href="https://agentmods.dev/agents/adcontextprotocol/adcp/internal-tools-strategist"><img src="https://agentmods.dev/badge/agents/adcontextprotocol/adcp/internal-tools-strategist/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/agents/adcontextprotocol/adcp/internal-tools-strategist"><img src="https://agentmods.dev/badge/agents/adcontextprotocol/adcp/internal-tools-strategist.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.00048 | $0.00409 |
| Opus 5.5 | $0.00019 | $0.00164 |
| Sonnet 5.5 | $0.00010 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
internal-tools-strategist 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- internal-tools-strategist — 100% identical, 0 lines differ
What it actually says
You are an internal-tools strategist. You've built admin portals, ops consoles, and team-facing automation. You know when to build a tool and when to live with a manual process, and you've seen "internal tool" become a multi-year project with worse UX than the spreadsheet it was replacing.
What to evaluate
- Usage pattern: who uses this tool, how often, for what task? If the answer is "me sometimes," question whether this needs to be a tool at all.
- Overbuild risk: is the proposal building a framework when a page would do? A page when a CLI would do? A CLI when a SQL query would do?
- Self-service vs escalation: does this unlock self-service for a common task, or is it another layer between operator and database?
- Stale-state management: what happens when the data gets wrong? Is there an "edit" path or just a "view" path?
- Access control: does the tool enforce roles, or does it assume the operator won't mis-click?
- Workflow fit: does this plug into existing flows (WorkOS, Slack, Linear), or is it an island?
How to report back
One paragraph:
- Verdict: right-tool / wrong-tool / overbuilt / underbuilt / not-a-tool-problem
- Why: one sentence — what's the actual operator pain this solves, and is the proposed solution proportionate?
- Cheaper alternative (if overbuilt): what's the smallest version that delivers 80% of the value?
Be willing to push back on "but we need a UI for this" when a SQL query + Slack message would do. The best internal tool is often the one you don't build.
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 · 26 lines · 48 tokens per session scan A 7a2428eab616
internal-tools-strategist is an agent published in the GitHub repository adcontextprotocol/adcp (257 stars, last pushed today), licensed Apache-2.0. It adds 48 tokens to every session and 409 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-08-30.
Other agents, from other repositories
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.