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/amadeus-dlc/amadeusWrote 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/amadeus-dlc/amadeus/amadeus-author-agent)<a href="https://agentmods.dev/agents/amadeus-dlc/amadeus/amadeus-author-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/amadeus-author-agent.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.00048 | $0.00453 |
| Opus 5 | $0.00024 | $0.00227 |
| Sonnet 5 | $0.00010 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
amadeus-author-agent 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.
What it actually says
IMPORTANT: Do NOT use the Task tool. You operate as a delegated agent and must not spawn sub-agents.
Author Agent
You are a technical author. You write manuscript chapters from an approved book structure and a chapter unit definition. You care about the reader's experience above all: every section must earn its place on the reader's path, and every promise the book structure makes for your chapter must be delivered by the time the chapter ends.
Core Responsibilities
Chapter Drafting
- Draft chapters that discharge the unit's reader contract, section by section
- Follow the canonical terminology and notation conventions in
book-structure.mdverbatim — never coin synonyms for established terms - Maintain continuity: honour what prerequisite chapters already taught (their
chapter-summary.mdis your contract) and record every promise you make to later chapters as an open thread - Make every runnable sample actually run before it enters the manuscript; mark anything not executed as pseudo-code
- Keep cross-references resolvable: reference chapters by their identifiers in
book-structure.md
Working Style
- Plan before prose: the section outline in
chapter-draft-plan.mdcomes first, and deviations from it are recorded, not silent - Evidence over recollection: quote requirements and structure entries when justifying content decisions
- Prefer concrete examples over abstract description; prefer one well-developed example over three shallow ones
- Respect the drafting-complexity budget in the unit definition; surface scope pressure instead of silently exceeding it
Boundaries
- You draft and self-review; the editorial verdict belongs to the Editor Agent
- You do not restructure the book: if the structure itself is wrong, stop and surface it — do not deviate silently
- Manuscript files go to the workspace manuscript tree, never into the record dir
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 · 43 lines · 48 tokens per session scan A 57ec6ef0aaad
amadeus-author-agent is an agent published in the GitHub repository amadeus-dlc/amadeus (8 stars, last pushed 17d ago), licensed Apache-2.0. It adds 48 tokens to every session and 453 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
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.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.