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 sehoon787/my-codex --skill boss-briefinggit clone --depth 1 https://github.com/sehoon787/my-codexWrote 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/sehoon787/my-codex/boss-briefing)<a href="https://agentmods.dev/skills/sehoon787/my-codex/boss-briefing"><img src="https://agentmods.dev/badge/skills/sehoon787/my-codex/boss-briefing/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/sehoon787/my-codex/boss-briefing"><img src="https://agentmods.dev/badge/skills/sehoon787/my-codex/boss-briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01813 |
| Opus 5.5 | $0.00009 | $0.00725 |
| Sonnet 5.5 | $0.00005 | $0.00363 |
| Haiku 4.5 | $0.00002 | $0.00181 |
Grade A, and why
boss-briefing 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 1mo 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boss Briefing Skill
Vault sync, workflow pattern analysis, and persona rule management. Run this skill during or at the end of a session to keep .briefing/ healthy and up to date.
This skill replaces the profile update functionality from stop-profile-update.js (which remains as a fallback for sessions where /boss-briefing is not run). The existing briefing-vault skill handles vault templates and initialization; this skill handles sync, analysis, and persona learning.
The my-codex runtime uses briefing-runtime.js for state management. State is stored in .briefing/state.json and can be read/written via standard filesystem operations.
Step 1: Read state.json
Read .briefing/state.json and extract session metadata:
date— session date (YYYY-MM-DD)workCounter— number of meaningful work eventssessionMessageCount— total prompts in this sessionlastVaultSync— ISO timestamp of last boss-briefing runsessionStartHead— git HEAD at session start (empty for non-git projects)promptCount— prompt countereditCount— edit countersubagentCount— subagent completion countersubagentSeq— sequential subagent index for agent-log enrichment
If state.json does not exist or is empty, report that and skip to Step 6.
Step 2: Previous Session Gap Detection
Compare the date field in state.json with today's date.
- If the gap is >= 1 day, scan
.briefing/sessions/for the most recent session file (by filename date prefix, excluding*-auto*files). - Report the gap: "N day(s) since last session on YYYY-MM-DD."
- If sessions exist, summarize the last session file's title/goal section for context recovery.
- If no previous sessions exist, note that this appears to be a fresh vault.
Step 3: Analyze agent-log.jsonl Sequences
Read .briefing/agents/agent-log.jsonl. Parse all entries from the last 30 days.
- Group entries by date (using the
tsfield, truncated to YYYY-MM-DD). - For each day, extract the ordered sequence of
agent_typevalues. - Look for recurring sub-sequences of length >= 2 that appear in >= 2 different sessions (days).
- Record each detected pattern with:
- The sub-sequence (e.g.,
explore → executor → code-reviewer) - How many sessions it appeared in
- The
phasemapping if available (e.g.,research → implement → review)
- The sub-sequence (e.g.,
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.
- 1mo ago First seen · 188 lines · 23 tokens per session scan A 4cb95074315c
boss-briefing is a skill published in the GitHub repository sehoon787/my-codex (29 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 1,813 once invoked, about $0.0001 per session on Opus 5.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
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…
hive-mind-advanced
Queen-led collective-intelligence coordination with consensus mechanisms and persistent shared memory. Use when orchestrating a large swarm of agents under a lead coordinator, building consensus across agents, or maintaining durable cross-agent memory.
compact-kb
Use only when user explicitly invokes $compact-kb.
maintain-codex-wiki
Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows…
context-loader
Load project context efficiently for Conductor workflows. Use when starting work on a track, implementing features, or needing project context without consuming excessive tokens.
add-new-entry-from-temp-md
Format new entries from temp.md into tempentries.md, ready to insert into the section files. USE FOR: adding new resources to the knowledge base. DO NOT USE FOR: editing existing entries or restructuring sections.