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 mishahanin/heading-os --skill event-debriefgit clone --depth 1 https://github.com/mishahanin/heading-osWrote 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/mishahanin/heading-os/event-debrief)<a href="https://agentmods.dev/skills/mishahanin/heading-os/event-debrief"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/event-debrief/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/mishahanin/heading-os/event-debrief"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/event-debrief.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.00089 | $0.01142 |
| Opus 5 | $0.00044 | $0.00571 |
| Sonnet 5 | $0.00018 | $0.00228 |
| Haiku 4.5 | $0.00009 | $0.00114 |
Grade A, and why
event-debrief 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 10d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event Debrief
Post-event recap with leads, follow-ups, lessons learned, and action items.
Variables
event: [Event name — MWC, regional expos, launch events, partner summit, etc.]
dates: [Event dates]
notes: [Paste raw notes, business cards collected, conversations had, impressions — as messy as needed]
outcome_assessment: strong | moderate | below-expectations — optional
Instructions
Before processing, read:
context/pipeline.md— Current pipeline to map new leads againstcontext/people.md— Check if any contacts from the event are already knowncontext/strategy.md— Strategic priorities to assess event ROI against
Process the raw notes and produce a structured debrief.
Event Debrief Structure
1. Executive Summary
- Event name, dates, location
- 31C's presence (booth, meetings, presentations)
- Overall assessment in one sentence
- Top 3 outcomes
2. Leads Generated
| Contact | Company | Role | Interest Level | Next Step | Owner | Deadline |
|---|---|---|---|---|---|---|
| Hot / Warm / Cold |
3. Meetings Held
For each meaningful meeting:
- Who: name, title, company
- What discussed: 2-3 sentences
- Their interest: what specifically resonated
- Commitment: what they said they'd do next
- Our follow-up: what we need to do, by when
- Pipeline impact: new opportunity / existing deal advancement / relationship building
4. Competitive Intelligence Gathered
- What competitors were present
- What they were saying/showing
- Any intel on their deals, positioning, or customer conversations
- Market sentiment observations
5. Market Signals
- Themes that kept coming up in conversations
- What buyers are actually asking for (vs. what we assumed)
- Regulatory or geopolitical signals
- Technology trends observed
6. What Worked
- Messages that resonated
- Materials or demos that generated interest
- Approach or positioning that landed
7. What to Improve
- What didn't land
- Gaps in our materials or pitch
- Logistics or preparation improvements for next time
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.
- 10d ago First seen · 142 lines · 89 tokens per session scan A f82091f70e3b
event-debrief is a skill published in the GitHub repository mishahanin/heading-os (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 89 tokens to every session and 1,142 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
shogun-bloom-config
An interactive wizard that creates model-routing settings from your AI subscription choices. Model routing decides which available model handles each kind of task.
shogun-model-list
A reference table of AI command-line tools, their available models, subscription requirements, and maximum Bloom capability levels. Bloom's Taxonomy is a scale describing thinking tasks, from remembering information to creating new designs.
shogun-model-switch
A live-switching tool for changing which command-line AI agent, model, and reasoning mode is running. It updates settings, restarts the agent, and refreshes the displayed session information.
shogun-screenshot
A screenshot tool for getting images from a computer or web page and then cropping, resizing, or masking sensitive information. Playwright is a browser-automation tool used here to capture web pages.
shogun-readme-sync
A skill that compares an English README with its Japanese counterpart and brings them back into alignment. A README is the project document that explains what the software is and how to use it.
shogun-agent-status
A skill that shows whether the agents in a multi-agent Japanese feudal-themed team are working, waiting, missing, or assigned tasks. It combines terminal session status, task files, and unread messages.