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 vincentmumme/personalos-boilerplate --skill analyse-callgit clone --depth 1 https://github.com/vincentmumme/personalos-boilerplateWrote 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/vincentmumme/personalos-boilerplate/analyse-call)<a href="https://agentmods.dev/skills/vincentmumme/personalos-boilerplate/analyse-call"><img src="https://agentmods.dev/badge/skills/vincentmumme/personalos-boilerplate/analyse-call/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/vincentmumme/personalos-boilerplate/analyse-call"><img src="https://agentmods.dev/badge/skills/vincentmumme/personalos-boilerplate/analyse-call.svg" alt="Reviewed on agentmods" width="80" 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.00058 | $0.01121 |
| Opus 5 | $0.00029 | $0.00561 |
| Sonnet 5 | $0.00012 | $0.00224 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
analyse-call 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 11d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: analyse-call
Contract
Dieser Skill überführt einen bereits lokal vorliegenden Call nachvollziehbar in PersonalOS-Kontext.
- Der Transkriptauszug oder die Meeting-Notiz bleibt als
source-evidenceerhalten. - Das Gespräch, seine Interpretation und die daraus übernommene aktuelle Wahrheit bleiben drei unterscheidbare Ebenen.
- Nur Aussagen, die der Beleg wirklich trägt, verändern Person, Company oder Projekt.
- Unsicherheit und ausdrückliche Nichtentscheidungen bleiben sichtbar.
- Bestätigte nächste Handlungen werden ausschließlich über [[skills/task-manager/SKILL|task-manager]] als Actions geführt.
- Eine Action erlaubt noch keine Nachricht, Einladung, Kalenderänderung oder andere externe Ausführung.
- Jede Änderung endet mit [[skills/pos-verify/SKILL|pos-verify]] auf der ausdrücklichen Dateiliste.
Ablauf
1. Quelle und Grenze lesen
Lies das Interaction Event und jede verknüpfte Evidence-Datei vollständig. Halte fest, was die Quelle belegt, was sie nicht belegt und ob der Inhalt real, anonymisiert oder fiktiv ist. Verändere Evidence nicht, um sie an die spätere Interpretation anzupassen.
2. Betroffenen Kontext laden
Lies nur die verknüpften oder eindeutig betroffenen Personen, Companies, Projekte, Actions und Systemregeln. Kläre vor dem Schreiben:
- Was gilt bereits?
- Was ist im Call wirklich neu?
- Welche Aussage ersetzt oder präzisiert bisherigen Stand?
- Welche offenen Punkte bleiben offen?
- Welche bestätigte Handlung gehört in Operations?
3. Analyse vor Propagation schreiben
Erstelle unter analysis/<uuid>.md eine interaction-analysis nach [[system/templates/interactions/interaction-analysis]]. Trenne Findings, Unsicherheit, Propagation und Quellen. Eine plausible Interpretation wird nicht allein dadurch zu Current Truth.
4. Kanonische Owner gezielt aktualisieren
Ändere nur die Abschnitte, deren aktueller Stand sich wirklich geändert hat. Formuliere Current Truth neu und gegenwartsbezogen, statt einen weiteren datierten Absatz anzuhängen. Geschichte und Belege bleiben in Timeline, Interaction und Evidence. Lege keine parallele Wahrheit in der Analyse an.
What ships with it
1 file 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.
- 11d ago First seen · 85 lines · 58 tokens per session scan A cb99d0067ed9
analyse-call is a skill published in the GitHub repository vincentmumme/personalos-boilerplate (19 stars, last pushed 16d ago), licensed MIT. It adds 58 tokens to every session and 1,121 once invoked, about $0.0003 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-31.
Other skills, from other repositories
lint-brain
Run health checks over the brain vault - find orphan notes, broken wikilinks, missing frontmatter, stale projects, and missing cross-links. Use when asked to "lint the brain", "health check", "vault hygiene", or "/lint-brain".
ingest-article
Ingest an article from a URL or raw text into the brain vault. Extracts key knowledge, determines placement, creates or updates notes, and links to relevant projects. Use when the user shares a URL or text and wants to absorb it into their knowledge base.
wrap-session-up
End-of-session review for a Claude Code conversation. Replays what was discussed, checks for open action items, documents relevant outcomes in the brain vault, and creates Todoist tasks for anything untracked. Use at the end of a work session to ensure nothing falls through the cracks.
kickoff
Guided first-run setup for a forked brain-starter vault. Walks through identity, first project, semantic search, integrations, indexes, and the first commit - verifying each phase before moving on. Use when the user has just forked or cloned brain-starter, says "set up my brain", "I just forked brain-starter", or runs…
project-sync
On-demand AI-powered sync of a project's repo state into the brain vault. Reads live git/GitHub/Jira data, updates the project status doc, and makes targeted edits to relevant brain docs where content is clearly stale. Triggered by "/project-sync [name]", "sync [project]", "what's the current state of [project]".
save-answer
File a conversation output (research, analysis, comparison, framework) back into the brain vault so it compounds instead of vanishing into chat history. Use when the user says "save this", "file this", "keep this", or when a valuable answer should persist.