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 bostonaholic/team --skill eng-design-doc-reviewgit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/eng-design-doc-review)<a href="https://agentmods.dev/skills/bostonaholic/team/eng-design-doc-review"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/eng-design-doc-review/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/bostonaholic/team/eng-design-doc-review"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/eng-design-doc-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 11 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 107 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 44 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 116 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00042 | $0.01889 |
| Opus 5 | $0.00021 | $0.00945 |
| Sonnet 5 | $0.00008 | $0.00378 |
| Haiku 4.5 | $0.00004 | $0.00189 |
Grade A, and why
eng-design-doc-review 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 6d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Design Doc Review — Independent Fresh-Context Audit
Adversarially review a design document with fresh context. The brief this
skill dispatches lives in skills/reviewing-designs/SKILL.md, and the
orchestrator loads the same brief for the DESIGN phase's adversarial
review gate. Invoking this skill standalone remains supported whenever
you want an independent, fresh-context audit of a design document.
Write the prose this skill governs at a seventh-grade reading level, in
STE-flavored mode — short sentences, common words, no unexplained jargon.
Full methodology: writing-prose. Before
you finalize prose this skill governs, call the Skill tool with
writing-prose and apply its ## Self-lint checklist.
There is no custom review agent. This skill loads the review brief
from reviewing-designs and dispatches the built-in read-only
Explore subagent through the Agent tool. That subagent boots with a
clean context and no shared conversation history with the design-author
— that isolation is the whole point. It prevents self-evaluation bias.
Explore holds no Write/Edit tools, so the reviewer structurally cannot
change the artifacts it judges.
Fresh context plus veto-without-authorship is the generator-evaluator rule (principle-generator-evaluator).
Input
$ARGUMENTS is the artifact directory: docs/plans/<id>/. If empty, the
discovery command below resolves it.
The review reads:
$ARGUMENTS/6-design.md— the document under review (required)$ARGUMENTS/1-task.md,$ARGUMENTS/2-questions.md,$ARGUMENTS/5-research.md,$ARGUMENTS/4-repos.md— predecessor artifacts (read for grounding when present, missing siblings are not a hard error)
Resolve <team-skill-dir> to the absolute directory containing
skills/team/SKILL.md. From the repository root, run:
"<team-skill-dir>/discover-topic.sh" "${ARGUMENTS:-}" "6-design.md"
- If the command printed a path, use it as
$ARGUMENTSfor the rest of this skill. That is tier 1 explicit arg, or tier 2 discovery. When the path came from tier 2, with no explicit arg, announce the resolved directory to the user first. An auto-picked topic is then never silent. - If the command printed nothing (tier 3 — no directory holds
6-design.md), do not hard-error. FireAskUserQuestionwith aSetupheader and labeled options:- Run the producer — run
/team-design docs/plans/<id>/to produce the missing6-design.md. - Give a path — the user supplies the
docs/plans/<id>/directory directly (runls docs/plans/to find your topic directory).
- Run the producer — run
What ships with it
1 file 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.
- 6d ago Changed · -32 lines · -75 tokens per session 65de3e63096f
- 7d ago Changed · -138 lines · +7 tokens per session 4499ae4672c7
- 11d ago First seen · 316 lines · 110 tokens per session scan A e8f2928ce0f9
eng-design-doc-review is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,889 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-30.
Other skills, from other repositories
codebase-sync
Convention discovery and rule generation from codebase analysis. Scans project structure, builds search indexes, identifies patterns, and generates enforceable rules.
code-review-patterns
Multi-dimensional code assessment across security, quality, performance, and maintainability with confidence-gated reporting (>=80%) and Router Contract generation.
code-review-orchestration
6-agent parallel code review orchestration covering architecture, security, performance, testing, quality, and documentation dimensions with weighted scoring.
code-review-pipeline
Multi-dimensional code review across correctness, security, performance, and maintainability with confidence-gated reporting and remediation loops.
plan-implementation
Disciplined execution of approved plans with step-by-step verification, phase checkpoints, failure investigation, and mandatory code/security reviews.
quality-checklist
Validate implementation quality through custom checklists, scoring against constitution standards, specification coverage, and producing remediation recommendations.