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 panaversity/agentfactory-business-plugins --skill executive-briefgit clone --depth 1 https://github.com/panaversity/agentfactory-business-pluginsWrote 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/panaversity/agentfactory-business-plugins/executive-brief)<a href="https://agentmods.dev/skills/panaversity/agentfactory-business-plugins/executive-brief"><img src="https://agentmods.dev/badge/skills/panaversity/agentfactory-business-plugins/executive-brief.svg" alt="Measured on agentmods" 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.00090 | $0.00725 |
| Opus 5 | $0.00045 | $0.00362 |
| Sonnet 5 | $0.00018 | $0.00145 |
| Haiku 4.5 | $0.00009 | $0.00072 |
Grade A, and why
executive-brief 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 8d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SITUATION BRIEF WORKFLOW
STEP 1 — LOAD CONTEXT
Read work.local.md in the current working directory.
If it does not exist, tell the user to run /agentic-office:setup first.
STEP 2 — IDENTIFY BRIEF TYPE
TYPE 1: PRE-MEETING BRIEF Purpose: Everything you need to know before a specific meeting. Input: Meeting name / attendees / agenda Output: Context per agenda item; stakeholder notes; decisions needed; prior meeting summary
TYPE 2: PRE-DECISION BRIEF Purpose: All relevant context before making a specific decision. Input: Decision to be made; who is affected; constraints Output: Decision context; options; relevant precedents; stakeholder positions
TYPE 3: PERSON BRIEF Purpose: Quick profile of someone you are about to interact with. Input: Person name Output: Role; current focus; communication style; today's context; approach tips
TYPE 4: PROJECT BRIEF Purpose: Current status of a project you need to speak about. Input: Project name Output: Status; current milestone; risks; decisions made; key contacts
TYPE 5: TOPIC BRIEF Purpose: Everything in workplace memory relevant to a topic. Input: Topic name Output: What is known across all memory layers; relevant decisions; open questions
STEP 3 — PRODUCE BRIEF
OUTPUT STRUCTURE:
SITUATION BRIEF — [Subject]
Prepared: [Date/Time] | For: [Name from work.local.md]
================================================================
THE SITUATION IN ONE SENTENCE:
[Most important thing to know — written as a colleague would say it]
CONTEXT:
[Background — what led to this; relevant history; decisions already made]
WHAT YOU NEED TO KNOW NOW:
[Current status; what is live; what has changed recently]
THE KEY QUESTION:
[The one thing that needs resolving — decision / answer / commitment]
STAKEHOLDER POSITIONS (if relevant):
[Person]: [Their likely position; what they need; how to approach]
RISKS:
[What could go wrong in this conversation / decision]
YOUR RECOMMENDED APPROACH:
[Specific guidance — not generic; based on work.local.md context]
================================================================
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.
- 8d ago First seen · 95 lines · 90 tokens per session scan A c734e1924814
executive-brief is a skill published in the GitHub repository panaversity/agentfactory-business-plugins (29 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 90 tokens to every session and 725 once invoked, about $0.0005 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
internal-linking-optimizer
An analysis tool for the links within a website. Internal links are links from one page of a site to another page on the same site.
geo-review-html
Render an interactive, self-contained HTML companion for a GEO content brief (04-content-brief) or a publish-ready draft (05-production), so a NON-technical client reviewer (founder, organizer staff, the domain expert filling slots) can fill REQUIRED-FILL slots, leave section-level comments, and approve/return work in…
memory-manage
Manage Active updates, atomic session handoffs, and human-gated Long-Term proposals. Use when asked to remember something, preserve a decision, log meaningful work, or review memory.
memory-read
Query-first indexing and retrieval for Operator OS memory. Use when asked to find prior context, search memory, rebuild the memory index, or answer from the workspace without loading large files by default.
weblyfe-landing-page
Build a complete conversion-optimized landing page for Weblyfe clients. Full pipeline from competitor audit through SEO analysis, brand style guide, Next.js build, and Vercel deploy. Use when building or rebuilding any client website from scratch.
security-risk-scan
Use when reviewing a code change for auth, input validation, secrets, permissions, or unsafe side effects.