Borrowing it
Nothing to install: this file belongs to amkisko/scout_apm_mcp.rb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/amkisko/scout_apm_mcp.rb/main/.agents/skills/engineering-audit/SKILL.mdgit clone --depth 1 https://github.com/amkisko/scout_apm_mcp.rbWrote 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/amkisko/scout_apm_mcp.rb/engineering-audit)<a href="https://agentmods.dev/skills/amkisko/scout_apm_mcp.rb/engineering-audit"><img src="https://agentmods.dev/badge/skills/amkisko/scout_apm_mcp.rb/engineering-audit/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/amkisko/scout_apm_mcp.rb/engineering-audit"><img src="https://agentmods.dev/badge/skills/amkisko/scout_apm_mcp.rb/engineering-audit.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.00130 | $0.00630 |
| Opus 5 | $0.00065 | $0.00315 |
| Sonnet 5 | $0.00026 | $0.00126 |
| Haiku 4.5 | $0.00013 | $0.00063 |
Grade A, and why
engineering-audit 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 4d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering audit
Use when asked for an engineering audit, systems review, hot-path analysis, Big-O review, pipeline-style inspection, resource and budget review, trace and identification review, or a product-health pass.
Read engineering-audit.md in this skill directory for dimensions, indicators, stage checks, boundary and control mode, optional product modes, finding format, and ranking. Read resource-and-budget.md and trace-and-identification.md for every tree that can execute. Skip those two files only when the tree never becomes executed bytes, and state that reason.
Read the matching optional file when the product has that surface: product-surface.md, privacy.md, performance.md, observability.md, security.md, contracts.md, learned-systems.md. Skip and state the reason when it does not. Stay on concepts. Do not require a named framework or vendor tool.
Quick reference
Pipeline:
ingress → app logic → cache → database → queue → worker → external API → egress
Order findings by danger, then certainty, then impact, then fix cost. Present the smallest credible fix before structural rewrite. Separate missing coverage from futile coverage. Indicators are categorizable, measurable, and representable.
When the system has external services, devices, operators, or physical actuators, also run boundary and control mode: who commands whom, interface deviations, and whether intended, commanded, reported, inferred, and physical state can diverge without an alarm.
When the product has a place the person can return to, also ask whether unknown identifiers, auth returns, forbidden, error-body status, timeouts, rate limits, 5xx survival of answers, write conflicts, system-initiated recreation, file controls, and deep links, live refresh, or reconnect that replace in-progress work stay honest for the person and for status-based counters.
For every tree that can execute, also run resource and budget mode: measure memory, CPU, storage, network, and energy against a named ceiling; label cheaper, smaller, or greener as inference until benched. Also run trace and identification mode: which emissions identify a person or device, which observers see them, and whether they appear in what this product showed the person for this run. Skip those two modes only when the tree never becomes executed bytes.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed · +17 lines · +114 tokens per session a71a20604a45
- 10d ago First seen · 21 lines · 16 tokens per session scan A bb1632f5ba75
engineering-audit is a skill published in the GitHub repository amkisko/scout_apm_mcp.rb (2 stars, last pushed yesterday), licensed MIT. It adds 130 tokens to every session and 630 once invoked, about $0.0006 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 skills, from other repositories
python-design-pattern
Python design patterns and anti-patterns. Use when designing new components, refactoring, reviewing code for common mistakes, choosing abstractions, or evaluating pull requests for structural issues like tight coupling, leaking internal types, or error handling problems.
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…
run-sequence
Manage CRM sequences end-to-end — list, create, enroll contacts, activate/deactivate, duplicate, and track performance. Use when someone says "what sequences do I have", "create a welcome sequence", "enroll this contact in a sequence", "add these leads to my nurture sequence", "deactivate the cold outreach sequence"…
code-standards
Code quality standards and style guide for reviewing pull requests.
pr-review-comments
Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line. Use when you have a list/JSON of review findings (each with a file path, line number, and a message such as summary/failurescenario) and want them published on a PR as inline review…