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.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.00567 |
| Sonnet 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 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.
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.
- 8d 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 (26 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,134 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-08-30.
Other skills, from other repositories
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…
ctxwise
Audit and optimize OpenAI Codex context locally, compile model and subagent profiles, detect capability drift, create redacted lockfiles, inspect model-visible prompt structure, and render honest token, credit, quota, or API-cost receipts. Use when the user explicitly invokes CtxWise or asks to run its installed CLI…
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".
cross-task-learner
Enable agent loops to learn from similar past tasks and share patterns across loops.
ralph-memory
Manage Al semantic memory entries — list, query, and clear lessons learned across loop iterations.
reflection-injection
Inject relevant past reflections into agent context at iteration start so agents learn from prior mistakes without repeating them.