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 skills add MayR-Labs/skills --skill engineeringgit clone --depth 1 https://github.com/MayR-Labs/skillsWrote 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/mayr-labs/skills/engineering)<a href="https://agentmods.dev/skills/mayr-labs/skills/engineering"><img src="https://agentmods.dev/badge/skills/mayr-labs/skills/engineering/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/skills/mayr-labs/skills/engineering"><img src="https://agentmods.dev/badge/skills/mayr-labs/skills/engineering.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.00029 | $0.00389 |
| Opus 5.5 | $0.00012 | $0.00156 |
| Sonnet 5.5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
mayrlabs-copywriting-engineering 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 12d 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
MayR Labs Copywriting Doctrine: Engineering
Purpose
To standardize the creation of high-quality technical documentation. Good engineering docs are the bedrock of maintainable software. They must be exact, structurally sound, and extremely context-rich without being verbose.
Audience
AI Agents acting as Technical Writers or Engineers drafting READMEs, pull request descriptions, system designs, or API docs.
Core Rules & Constraints
1. Document Structure
- Context First: Always begin by answering Why this exists, the problem it solves, and its high-level goal.
- Prerequisites & Setup: Provide exact, copy-pasteable bash commands. Specify environment dependencies explicitly.
- Architecture: Do not just list files; explain data flow and component relationships. Use Markdown mermaid diagrams when beneficial.
2. Exactness
- Do not say "run the build script." Say: "Run
npm run buildto compile the artifacts to/dist". - Hardcode paths relative to the project root unless specified otherwise.
- In tutorials or examples, provide the expected output of successful commands.
3. Tone
- Objective, factual, and strictly professional.
- Highlight breaking changes or destructive operations with GitHub-style alerts
(e.g.,
> [!WARNING]).
Inputs & Outputs
- Input: Instructed to document an API, write a README, or explain a system.
- Output: A Markdown document featuring precise setup commands, architectural explanations, and clear context.
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.
- 12d ago First seen · 54 lines · 29 tokens per session scan A 5d061b508fb9
mayrlabs-copywriting-engineering is a skill published in the GitHub repository MayR-Labs/skills (0 stars, last pushed 18d ago), licensed MIT. It adds 29 tokens to every session and 389 once invoked, about $0.0001 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-10-02.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…