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 briefing-vaultgit 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/briefing-vault)<a href="https://agentmods.dev/skills/sehoon787/my-codex/briefing-vault"><img src="https://agentmods.dev/badge/skills/sehoon787/my-codex/briefing-vault/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/briefing-vault"><img src="https://agentmods.dev/badge/skills/sehoon787/my-codex/briefing-vault.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.00028 | $0.01134 |
| Opus 5.5 | $0.00011 | $0.00454 |
| Sonnet 5.5 | $0.00006 | $0.00227 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
briefing-vault 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- briefing-vault — 92% identical, 1 lines differ
How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Briefing Vault Skill
Manage the .briefing/ directory as a persistent, Obsidian-compatible knowledge base.
Initialize Vault
When starting a new vault (first time in a project):
- Create directory structure:
.briefing/
├── INDEX.md
├── sessions/
├── decisions/
├── learnings/
├── references/
└── agents/
- Create
.briefing/INDEX.md:
---
date: <today>
type: index
tags: [project, index]
---
# <Project Name> Knowledge Base
## Overview
<Brief project description>
## Recent Decisions
<!-- Auto-updated by agents -->
## Open Questions
<!-- Track unresolved items -->
## Key Links
- [[sessions/]] — Session logs
- [[decisions/]] — Architecture decisions
- [[learnings/]] — Patterns and solutions
- Add
.briefing/to.gitignore
Note Templates
Session Note (sessions/YYYY-MM-DD-topic.md)
---
date: YYYY-MM-DD
type: session
tags: [session]
related: []
---
# Session: <Topic>
## Goal
<What was requested>
## Actions
- <What was done>
## Results
- <Outcomes>
## Decisions Made
- [[decisions/decision-name]] — <brief>
## Learnings
- [[learnings/learning-name]] — <brief>
## Next Steps
- <Follow-up items>
Decision Note (decisions/name.md)
---
date: YYYY-MM-DD
type: decision
tags: [architecture|design|tooling]
status: accepted|superseded|deprecated
related: []
---
# Decision: <Title>
## Context
<Why this decision was needed>
## Options Considered
1. <Option A> — pros/cons
2. <Option B> — pros/cons
## Decision
<What was chosen and why>
## Consequences
<Impact of this decision>
Learning Note (learnings/name.md)
---
date: YYYY-MM-DD
type: learning
tags: [pattern|gotcha|solution]
related: []
---
# <Title>
## Problem
<What went wrong or was non-obvious>
## Solution
<What fixed it>
## Why It Works
<Root cause explanation>
Reference Note (references/name.md)
---
date: YYYY-MM-DD
type: reference
source: <URL or source description>
tags: [reference, topic]
related: []
---
# <Title>
## Source
<URL or citation>
## Key Points
- <Main finding 1>
- <Main finding 2>
## Context
<Why this reference is relevant>
## Raw Notes
<Verbatim excerpts or detailed notes>
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 · 244 lines · 28 tokens per session scan A 6e06da8611d7
briefing-vault is a skill published in the GitHub repository sehoon787/my-codex (29 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 1,134 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
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…
quick-learning
Owner of the unified methodology knowledge system: format, triad structure, similarity check, Seen counters, and Adapted tracking. Signal-gated: skips clean sessions automatically (zero cost). Automatic trigger: called by feature-execution, do-task, and design-generate (context exhaustion). Use when: "quick learning"…
vellum-memory-v3-migration
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.
context-engineering
A project documentation framework that records a project's goals, requirements, roadmap, and current state in separate files. It also keeps those documents within set size limits for an AI coding agent.
waggle-recall
Recall project-scoped Waggle history about a topic, component, decision, bug, experiment, or implementation attempt.