Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/softspark/ai-toolkitnpx agentmods add skills/softspark/ai-toolkit/briefingWrote 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/softspark/ai-toolkit/briefing)<a href="https://agentmods.dev/skills/softspark/ai-toolkit/briefing"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/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/softspark/ai-toolkit/briefing"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 86 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00032 | $0.01344 |
| Opus 5.5 | $0.00013 | $0.00538 |
| Sonnet 5.5 | $0.00006 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade B, and why
briefing scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`ai-toolkit install` wires `~/.claude/settings.json` to `app/hooks/ai-toolkit-statusline.sh`. The hook reads native Claude Code statusLine stdin (no session JSONL parsing) and renders one line: How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Briefing Command
Triggers the Chief of Staff to generate an executive summary.
Usage
/briefing [period]
# Example: /briefing today
# Example: /briefing week
/briefing --tokens [--since 7d|24h|30m]
# Reports real session token usage from Claude Code JSONL.
Protocol
- Collect: Gather logs from
kb/learnings/,maintenance/logs, and recent runs. - Synthesize: Group by category (Ops, Strategy, Actions).
- Filter: Remove low-priority success logs.
- Present: Render the Daily Brief.
Example
## Daily Brief — 2026-04-23
### Ops
- night-watch: 3 dep updates shipped, 1 rolled back (breaking change in `[email protected]`)
- health: all green except `mailpit` (degraded, non-critical)
### Strategy
- predict: new PR #42 overlaps with in-flight refactor in `/src/auth`
### Actions needed
- Review rollback from night-watch (ETA: 5 min)
- Decide on `x-pkg` pin strategy (open question on GitHub #41)
Rules
- MUST stay under 200 words unless the user explicitly asks for more detail
- MUST lead with decision-relevant facts, not chronology — "what should I act on" before "what happened"
- NEVER invent agent activity — report only what the logs show; absence of logs means "no data", not "nothing happened"
- CRITICAL: separate Ops (what ran) from Strategy (what was decided) from Actions (what needs a human) — mixing them defeats the brief
- MANDATORY: when no material activity exists for a category, omit the category heading instead of writing "none"
Gotchas
kb/learnings/often mixes drafts with completed entries. Filter by frontmatterstatus: finalor by filename convention before aggregating.maintenance/branch logs from/night-watchuse a different format (Shift Report markdown) than agent run logs. Do not concatenate blindly — parse each source separately and normalize.- "Recent runs" without an explicit time bound defaults to everything on some log backends. Always pass
--sinceor a date filter, or you will read a week into yesterday's memory. - Successful runs outnumber interesting runs by an order of magnitude. Aggressively filter green/noop entries — they are the signal's noise floor.
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 · 129 lines · 32 tokens per session scan B 47c662ff29af
briefing is a skill published in the GitHub repository softspark/ai-toolkit (181 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 1,344 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
work-autonomous
Abbruchbedingung für autonome Loops: So weit wie möglich selbständig weiterarbeiten UND einen Loop erst beenden, wenn belegt ist, dass keine autonom ausführbare Aufgabe mehr vorliegt. Der bloße Eindruck "nichts mehr zu tun" reicht NICHT — er löst eine vierstufige Prüfkette aus (think/decide, CONTROL/DECISIONS…
rotation-check
Standard-Gerüst für rotierende Pipeline-Checks: Pro Lauf genau ein Ziel aus einer Menge (Projekte, Ordner, Repos) wählen — bevorzugt das am längsten ungeprüfte —, den Check durchführen, Ergebnis in einer Check-Registry und einem Verlaufslog festhalten. Nutze diesen Skill, wenn ein wiederkehrender Check über viele…
kalender
Calendar skill with user-adaptive backend selection (Flag 3). Default: local SQLite store. Optional: Google Calendar MCP, Routinika or UpToday as backend — controlled via assist/prefs.json. Without preference the LLM asks the user interactively.
bewerbungsexperte
Spezialist fuer den gesamten Bewerbungsprozess. Analysiert Stellenanzeigen, optimiert Profile (LinkedIn/CV) und generiert massgeschneiderte Anschreiben. Generiert ASCII-Lebenslaeufe aus einer SQLite-Datenbank und Ordnerstruktur. cvgenerator.py ist standalone portiert -- keine BACH-Runtime noetig.
folder-flattening
Verschachtelte Ordnerhierarchien in flache, maschinenlesbare Strukturen umbauen. Bash-basiert mit intelligenter Merge-Logik.
batch-file-ops
Batch-Dateioperationen (Löschen, Verschieben, Kopieren, Auflisten) mit Glob-Mustern. CLI-Werkzeug für effiziente Dateisystem-Operationen. Ohne Abhängigkeiten.