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.
git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kitWrote 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/commands/giuseppe-trisciuoglio/developer-kit/devkit.write-a-minute-of-a-meeting)<a href="https://agentmods.dev/commands/giuseppe-trisciuoglio/developer-kit/devkit.write-a-minute-of-a-meeting"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.write-a-minute-of-a-meeting/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/commands/giuseppe-trisciuoglio/developer-kit/devkit.write-a-minute-of-a-meeting"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.write-a-minute-of-a-meeting.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.00023 | $0.00575 |
| Opus 5 | $0.00012 | $0.00287 |
| Sonnet 5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
devkit.write-a-minute-of-a-meeting 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 today.
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Generates professional meeting minutes from transcripts or notes. Use when you need to create structured meeting documentation after a meeting.
Act as an expert administrative assistant specialized in creating meeting minutes. Analyze the provided transcript or notes and produce a clear, concise, and professional meeting minute document.
Usage
/devkit.write-a-minute-of-a-meeting $ARGUMENTS
Arguments
| Argument | Description |
|---|---|
$ARGUMENTS |
Combined arguments passed to the command |
Execution Instructions
Agent Selection: To execute this task, use the following approach:
- Primary: Use
general-purposeagent with appropriate domain expertise - Or use specialized agent if available for the specific task type
Input
Read the meeting transcript from: $1
Meeting Information Template
Use these details or ask for them if not provided:
- Meeting Title/Subject: $2
- Date and Time: $3
- Location/Platform: (e.g., Teams, Zoom, in-person)
- Attendees: (list participants)
- Meeting Objective: (purpose of the meeting)
Document Structure
Create the meeting minutes with the following sections:
1. Executive Summary
Begin with a brief paragraph (3-4 sentences maximum) summarizing the main outcomes and key decisions from the meeting.
2. Agenda Items Discussed
For each agenda item, create a dedicated section that includes:
- Clear and concise summary of the discussion
- Significant contributions from participants, properly attributed
- Conclusions reached for each item
3. Decisions Made
Extract and list all final decisions approved during the meeting. For each decision, specify:
- The decision itself
- Who proposed/approved the decision
4. Action Items
Create a table with the following columns:
| Action | Responsible | Deadline |
|---|---|---|
| Description of the task | Person or team assigned | Completion date |
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.
- today First seen · 98 lines · 23 tokens per session scan A 81173ed2d210
devkit.write-a-minute-of-a-meeting is a command published in the GitHub repository giuseppe-trisciuoglio/developer-kit (343 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 575 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-09-10.
Other commands, from other repositories
close-the-quarter
Workflow recipe — turn the quarter's raw numbers into a leadership story and board deck by chaining 4 skills.
exec-summary
Compress a document or update into a crisp executive summary.
prd
Draft a product requirements document from a feature idea or brief.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.