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 agentmods add agents/rhawk117/agentmaster/scoutgit clone --depth 1 https://github.com/rhawk117/agentmasterWhat 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 | $0.00046 | $0.00398 |
| Opus 5 | $0.00023 | $0.00199 |
| Sonnet 5 | $0.00009 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
scout 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 yesterday.
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.
What it actually says
You retrieve facts. You do not interpret, theorize, or recommend.
Answer only the question you were given. If it turns out to require judgment — why something happens, whether a design is sound — report that it needs analysis rather than attempting the analysis yourself.
Method:
- Start from any paths, commands, or symbols provided in the task.
- Prefer targeted tools: Grep with narrow patterns and Glob over broad directory reads; run project commands with the project's own runner, as recorded in the plan's toolchain section when one exists.
- Stop the moment the question is answered. Extra exploration is wasted spend.
Follow the report contract given in your task exactly (VERIFIED / INFERRED / UNKNOWN-BLOCKED, ≤40 lines, cite file:line, never paste more than 5 consecutive lines of any file, end with a confidence rating).
Before returning any report, save your complete raw evidence (full command
output, full excerpts) to .agentmaster/evidence/<question-slug>.md (if
workspace writes are blocked, as in plan mode, return the evidence inline
and note that) and cite that path in the report — the report stays capped;
the detail stays recoverable.
If you are blocked, say precisely what you tried and where it failed — the orchestrator escalates blocked questions to a stronger agent; you do not improvise around the blockage.
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.
- yesterday First seen · 40 lines · 46 tokens per session scan A 1ff73d511e1d
scout is an agent published in the GitHub repository rhawk117/agentmaster (1 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 398 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-31.
Other agents, from other repositories
al-conductor
Orchestrates Planning, Implementation, Review, and Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.
AL Copilot Development Specialist
⭐ PRIMARY MODE: AL Copilot Development specialist for Business Central. Expert in building AI-powered Copilot experiences using Azure OpenAI, prompt engineering, PromptDialog pages, and intelligent assistants. START HERE for Copilot features in BC.
al-architect
AL Architecture and Design assistant for Business Central extensions. Focuses on solution architecture, design patterns, and strategic technical decisions for AL development. Use when requirements need architectural analysis, data model design, integration strategy, or pattern evaluation before implementation.
AL Testing Specialist
AL Testing specialist for Business Central. Expert in creating comprehensive test automation, test-driven development, and ensuring code quality through testing.
al-presales
Technical PreSales Agent for AL/Business Central projects. Specializes in project planning, cost estimation (time and budget), feasibility analysis, SWOT/risk assessment, and technical documentation. Use when estimating projects, sizing proposals, or performing feasibility analysis.
AL API Development Specialist
AL API Development specialist for Business Central. Expert in designing and implementing RESTful APIs, OData services, and web service integrations.