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 agentmods add instructions/silverstein/minutes/agents-mdgit clone --depth 1 https://github.com/silverstein/minutesWhat 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 | $0.03234 | $0.03234 |
| Opus 5 | $0.01617 | $0.01617 |
| Sonnet 5 | $0.00647 | $0.00647 |
| Haiku 4.5 | $0.00323 | $0.00323 |
Grade C, and why
minutes AGENTS.md scanned grade C with 2 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf directory # NOT: rm -r directory Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
PUBLISHED=$(curl -s https://crates.io/api/v1/crates/whisper-guard | jq -r '.crate.max_stable_version') How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This project uses bd (beads) for issue tracking. Run bd onboard to get started.
In this repo, beads is local-only: use it for structured issue tracking on your machine, but do not expect a shared Dolt remote.
Quick Reference
bd ready # Find available work
bd show <id> # View issue details
bd update <id> --claim # Claim work atomically
bd close <id> # Complete work
GitHub Discussions
This repo has GitHub Discussions enabled (silverstein/minutes). Issues are for bugs and feature requests. Discussions are for usage questions, setup help, and community show-and-tell.
Agent guidelines:
- When triaging an issue that's really a "how do I...?" question, suggest converting it to a Discussion rather than closing it
- When a user's bug report turns out to be a config/setup issue, answer it and note that Discussions is the better venue for follow-ups
- After shipping a feature or fix, check if any open Q&A discussions are resolved by the change — post a reply pointing to the release
- When writing user-facing error messages or help text, link to Discussions (not Issues) for support:
https://github.com/silverstein/minutes/discussions - Don't file Discussions as work items — they're community conversations, not tracked tasks
Portable Agent Skills (.agents/skills/minutes/, .opencode/skills/)
This repo maintains skill outputs in three locations:
.claude/plugins/minutes/— Claude Code plugin (uses${CLAUDE_PLUGIN_ROOT}).agents/skills/minutes/— Agent-agnostic mirror for Codex, Gemini, Pi, and other agents (uses$MINUTES_SKILLS_ROOT).opencode/skills/— OpenCode-native mirror (one-level discovery path + matching.opencode/commands/)
What lives where:
SKILL.mdfiles are mirrored 1:1. Content is identical except for path variables and platform-specific references (e.g., "open in desktop app" in the plugin version becomes a CLI command in the agents version)._runtime/hooks/lib/containsminutes-learn.mjsandminutes-learn-cli.mjs— the behavioral learning system. These must stay byte-identical across.agents/skills/minutes/_runtime/hooks/lib/and.opencode/skills/_runtime/hooks/lib/.- Bundled scripts (for example
scripts/tag_apply.py) are mirrored into both portable trees. .opencode/commands/*.mdprovides native/minutes-*slash commands for OpenCode and is generated from the same canonical skill sources.
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.
- 2d ago First seen · 272 lines · 3,234 tokens per session scan C 8b2c3431d2e9
minutes AGENTS.md is an instructions file published in the GitHub repository silverstein/minutes (1,458 stars, last pushed today), licensed MIT. It adds 3,234 tokens to every session, about $0.0162 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vexa AGENTS.md
AGENTS.md instructions for Vexa-ai/vexa, covering agents.md — the agent front door (in-repo), researching vexa? start here, driving vexa from an agent session, your issue is your prd and claiming — and say hello on discord.
stenoai CLAUDE.md
Instructions for stenolabs/stenoai, covering claude.md, architecture, development commands, backend (python) and desktop app (electron).
vexa CLAUDE.md
Claude Code instructions for Vexa-ai/vexa, a project described as: Open-source meeting transcription API for Google Meet, Microsoft Teams & Zoom. Auto-join bots, real-time WebSocket transcripts, MCP server for AI agents. Self-host or use hosted SaaS.
stenoai AGENTS.md
Instructions for stenolabs/stenoai, covering agents.md, code review rules, bundled binaries with an api, bare exit() in python and platform parity.
os-clovy AGENTS.md
Instructions for open-software-network/os-clovy, covering clovy — agent instructions, project, os platform (shared brain), structure and domain & decisions — read before writing code.
Logue CLAUDE.md
Instructions for bitwize-ai/Logue, covering logue — development guidelines, project overview, running the build you just made, where documentation goes and dependencies.