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 skills/thermiteau/maverick/do-adoptnpx skills add thermiteau/maverick --skill do-adoptgit clone --depth 1 https://github.com/thermiteau/maverickWrote 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/skills/thermiteau/maverick/do-adopt)<a href="https://agentmods.dev/skills/thermiteau/maverick/do-adopt"><img src="https://agentmods.dev/badge/skills/thermiteau/maverick/do-adopt.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.00061 | $0.01622 |
| Opus 5 | $0.00030 | $0.00811 |
| Sonnet 5 | $0.00012 | $0.00324 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
do-adopt 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 5d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adopt Best-Practice Technologies
Scan the current project for missing best-practice areas and implement the top recommendation for each gap — or, in recommend mode, stop after producing recommendations without installing anything.
Modes and Invocation
$ARGUMENTS may contain a topic name, the word recommend, or both:
- (empty) — adopt every gap topic in the table below.
<topic>— adopt that one topic only.recommend [<topic>]— recommend-only mode: perform the same detection and analysis, write the recommendation as astatus: recommendedproject skill (see step 5R), and implement nothing. This replaces the old standalonedo-recommendskill.
Do not prompt the user for which topics to process.
Topics
| Topic | Best-Practice Skill |
|---|---|
| linting | mav-bp-linting |
| unit-testing | mav-bp-testing |
Detection hints for each topic come from the shared registry —
${CLAUDE_PLUGIN_ROOT}/skills/do-upskill/topics.json (scanHints per
topic). Do not maintain a separate detection list here.
Process
For each topic:
1. Check Whether the Practice Already Exists
Apply the topic's scanHints (dependencies, grep patterns, file globs)
plus a check for CI steps that run the tool. If the practice is
already implemented (configs exist, dependencies present, actively
used), skip the topic. Print: <topic>: already implemented, skipping.
2. Identify the Project's Tech Stack
Determine the primary language(s) and framework(s) by reading:
package.json(Node/JS/TS, look at framework deps like react, vue, express, etc.)pyproject.toml/requirements.txt(Python)go.mod(Go)Cargo.toml(Rust)build.gradle.kts/pom.xml(JVM)- Source file extensions and directory structure
3. Read the Best-Practice Skill
Read the corresponding best-practice skill
(${CLAUDE_PLUGIN_ROOT}/skills/<skill-name>/SKILL.md) to understand the
recommended tools and configuration standards for the detected stack.
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.
- 5d ago First seen · 135 lines · 61 tokens per session scan A a19ff0b90f06
do-adopt is a skill published in the GitHub repository thermiteau/maverick (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,622 once invoked, about $0.0003 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-30.
Other skills, from other repositories
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
detect-flaky-tests
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
add-go-test
Write or extend Go unit tests in this repo. Use when the user asks to add or update Go tests.