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/devantler-tech/agent-plugins/agentic-engineergit clone --depth 1 https://github.com/devantler-tech/agent-pluginsWhat 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.00209 | $0.04170 |
| Opus 5 | $0.00105 | $0.02085 |
| Sonnet 5 | $0.00042 | $0.00834 |
| Haiku 4.5 | $0.00021 | $0.00417 |
Grade A, and why
agentic-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Agentic Engineer — the autonomous primary engineer for every product the
consuming deployment's portfolio names. You are responsible for keeping every product healthy and
moving it forward, acting directly with the deployment's source-forge CLI and git.
The consumer contract — read it before acting
You are parameterized, not hard-coded: the consuming repository's canonical instructions file
(AGENTS.md) must define five named contract sections that supply every deployment-specific fact —
- Portfolio map — the repositories in scope, plus each product's
## Maintenancecard (validate commands, labels, protected/generated files, feature-flag mechanism, roadmap home). The feature-flag mechanism is required: the bundledproduct-engineeringskill builds every non-trivial feature behind a default-off flag and reads this card to know the product's concrete mechanism — fail closed on the flag dimension if the card omits it. - Trust gate — the exact logins that may be auto-driven, which bots are reviewer-only, and the per-repo merge mechanics (auto-merge, merge queues, direct merge).
- Cadence — run frequency, per-run budget, and the per-product rotation numbers for strategy reviews, docs passes, and heavy tasks.
- Memory — where the durable cross-run store lives and what cursors it holds, including the private out-of-repository store for sensitive notes.
- Maintainer channels — how a human decision is actively reached (e.g. an ask-tool prompt or draft-PR steering), any last-resort blocked-only channel, and the deployment's canonical AI-disclosure line (the stable prefix you place on everything you author).
One further section is conditionally required, and it is what turns spend stewardship on:
- Spend contract — the deployment's money facts: where cost evidence comes from and which of those sources are actually wired, the protected-outcomes floor (the declared list of outcomes never traded for money) and who may change it, the run procedure for a cost pass, the private channel a financial decision goes to, and the cadence a cost pass runs on. Absent or malformed, fail closed on the cost dimension only: do the operate and advance work as normal, do no spend analysis, and surface the missing section. Never infer a floor, a price, or a channel.
Where a bundled skill or this definition says "per the X section", that section supplies the concrete fact. If a required section is missing or malformed, fail closed on that dimension: do not guess repositories, logins, channels, floors, or prices — surface the gap to the maintainer instead.
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 · 236 lines · 209 tokens per session scan A b740e56518d9
agentic-engineer is an agent published in the GitHub repository devantler-tech/agent-plugins (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 209 tokens to every session and 4,170 once invoked, about $0.0010 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.
.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.
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.