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 authoring-designsgit 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/authoring-designs)<a href="https://agentmods.dev/skills/bostonaholic/team/authoring-designs"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/authoring-designs/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/authoring-designs"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/authoring-designs.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.00027 | $0.00797 |
| Opus 5 | $0.00014 | $0.00398 |
| Sonnet 5 | $0.00005 | $0.00159 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
authoring-designs 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring Designs
Confirm repo scope, resolve choices autonomously as recorded assumptions, and write 6-design.md. Use seventh-grade STE-flavored prose; call the Skill tool with writing-prose and apply ## Self-lint before finalizing.
If 1-task.md references 3-prd.md, read it first and follow “Consuming a PRD downstream” in skills/product-requirements-doc/SKILL.md.
Confirm repo scope
If docs/plans/<id>/4-repos.md exists, treat it as the working scope and name each affected repo in ## Decisions made.
If absent but 5-research.md indicates multiple repos, resolve each candidate autonomously. Require <name> to match ^[A-Za-z0-9._-]+$ and not equal . or ..; reject separators, absolute paths, traversal, and shell metacharacters. Resolve only <root>/../<name>, confirm its .git with Glob/Read (the questioner uses git -C <path> rev-parse --git-dir), and never record a path unless verified as a direct child of the home repo's parent.
When all candidates resolve, write docs/plans/<id>/4-repos.md from skills/artifact-frontmatter/SKILL.md before drafting. If any fails, remain single-repo and name the omitted repo/work in ## Risks. Never silently expand repo scope.
Resolve choices autonomously
Never pause for user input. Record every resolved choice in ## Decisions made as “Assumption — chosen without user review”; defer only low-stakes items to ## Open questions (deferred) (principle-record-assumptions). On revision, address reviewer findings verbatim and record new assumptions the same way.
Call the Skill tool with decision-making before resolving a technical choice
with two or more viable options. Record its decision basis with the assumption.
Design contract
Read references/design-template.md before drafting. The required sections are ## Current state, ## Desired end state, ## Patterns to follow, ## Decisions made, ## Out of scope, optional ## Surfaces, ## Open questions (deferred), and ## Risks.
What ships with it
2 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.
- yesterday Changed · +3 lines d5c9954b053e
- 4d ago Changed · -129 lines · -27 tokens per session 1f3759e5a3f2
- 6d ago Changed · +10 lines 592019b05273
- 10d ago First seen · 155 lines · 54 tokens per session scan A 5308a6f68172
authoring-designs is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 797 once invoked, about $0.0001 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
tutti-agent-workspace-app
Build or evolve a complex agent-enabled Tutti workspace app repository. Use for Tutti apps with web/server/shared monorepos, @tutti-os/agent-acp-kit local agent runtimes, kit-owned TUTTICLI agent/composer discovery, dynamic agent catalogs, run-scoped MCP tool gateways, app-owned package builders, web-first debugging…
assimilate-popular-workflows
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable…
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
mcp-app-verification
Comprehensive verification checklists for MCP Apps. Tests with basic-host reference, validates handler-before-connect, text fallback, resource URI linking, single-file bundling, host styling, CSP, and legacy pattern detection.
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
verification-suite
Plan structure validation, phase completeness checks, reference integrity verification, and artifact existence confirmation. Provides the structured verification layer ensuring GSD artifacts are well-formed and complete.