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 AlpacaLabsLLC/skills-for-architects --skill meeting-minutesgit clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architectsWrote 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/alpacalabsllc/skills-for-architects/meeting-minutes)<a href="https://agentmods.dev/skills/alpacalabsllc/skills-for-architects/meeting-minutes"><img src="https://agentmods.dev/badge/skills/alpacalabsllc/skills-for-architects/meeting-minutes/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/alpacalabsllc/skills-for-architects/meeting-minutes"><img src="https://agentmods.dev/badge/skills/alpacalabsllc/skills-for-architects/meeting-minutes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Prompt Injection · line 16 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Agent Snooping · line 85 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.00072 | $0.01957 |
| Opus 5 | $0.00036 | $0.00979 |
| Sonnet 5 | $0.00014 | $0.00391 |
| Haiku 4.5 | $0.00007 | $0.00196 |
Grade A, and why
meeting-minutes 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/as:meeting-minutes — Typed Project Meeting Records
Harness note: use
/as:<skill>on Claude Code and$<skill>on Codex. Resolve<skill-root>as the directory containing this loadedSKILL.mdand<plugin-root>as the plugin root that containsskills/, and use equivalent native tools when host tool names differ.
Create an auditable record of what occurred in a meeting without silently turning discussion into project facts, durable decisions, or assigned tasks.
Usage
/as:meeting-minutes from notes/owner-meeting.md
/as:meeting-minutes turn this transcript into minutes
/as:meeting-minutes revise meetings/2026-07-21-design-team.md
Hard rules
- Minutes are an event record. They record the meeting; they do not become the authority for current project facts, durable rationale, or task status.
- Save before promotion. Complete and save the minutes before offering any follow-up. Saving must not create or modify
PROJECT.md,decisions/*.md, orTASKS.md. - Promote item by item. Show separately labeled candidates and require the user to select each fact, decision, or task. A general request to save minutes is not promotion approval.
- Preserve epistemic status. Discussion, stated information, confirmed decisions, proposed decisions, proposed tasks, and open questions remain separate. Do not upgrade a statement or proposal based on confident wording.
- Preserve dates and provenance. Record the meeting's event date, the artifact creation date, and every source/input reference. Do not replace an event date with a transcript, file, commit, or modification timestamp.
- Never overwrite implicitly. A filename collision creates a deterministic numeric suffix. Update an existing record only when the user explicitly requests a revision of that record.
- Use portable links. Store project-relative Markdown paths, optionally with a heading or item label. Never persist machine-specific absolute paths.
- Do not fabricate gaps. Unknown attendees, dates, owners, due dates, or outcomes stay
UnknownorNot recorded. Ask only when a missing value materially changes the record.
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.
- 12d ago First seen · 126 lines · 72 tokens per session scan A 35ca16481e5d
meeting-minutes is a skill published in the GitHub repository AlpacaLabsLLC/skills-for-architects (353 stars, last pushed 8d ago), licensed MIT. It adds 72 tokens to every session and 1,957 once invoked, about $0.0004 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
cre-development
CRE Development and Construction suite - 8 specialist skills for U.S. site/entitlement screening, budget and yield-on-cost, construction loan sizing, GC contracts, draw review, schedule risk, lease-up pro forma, and IC memo writing.
github-issue-planning
Issue-backed plan persistence on GitHub via one managed issue comment with an idempotent marker. Prefers GitHub MCP when available and falls back to gh CLI when MCP is unavailable or misconfigured. Uses local plan persistence only when issue persistence is unavailable or not desired.
technical-roadmap-planning
Gathers inputs, defines initiatives, prioritises with an impact/effort matrix, sequences dependencies, and produces a roadmap table. Invoked when the user asks to plan a technical roadmap, prioritise engineering initiatives, or create a quarter/half-year engineering plan.
module-federation-ssr
Add, review, or debug server-side rendered Module Federation applications, including Modern.js, Nuxt, Next.js legacy Pages Router, Vinext, Vite SSR, and dual browser/server remote artifacts.
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
sparc-pipeline
Use when you need to run the full 5-phase SPARC methodology (Specification→Pseudocode→Architecture→Refinement→Completion) for a complex feature. Each phase has explicit done-criteria gates.