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.
git clone --depth 1 https://github.com/lckx777/copy-chief-blackWrote 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/commands/lckx777/copy-chief-black/dossier)<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/dossier"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/dossier/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/commands/lckx777/copy-chief-black/dossier"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/dossier.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.00000 | $0.00889 |
| Opus 5 | $0.00000 | $0.00445 |
| Sonnet 5 | $0.00000 | $0.00178 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
dossier 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 9d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dossier — Knowledge Dossier Management
Create, update, search, and merge knowledge dossiers. Dossiers are append-only knowledge bases organized by entity type.
Subcommands
/dossier create
Create a new dossier. Types: person, company, niche, mechanism, concept.
Examples:
/dossier create person "Dr. Klaus Richter"
/dossier create mechanism "Cristais de Otolitos"
/dossier create niche saude
/dossier add "fact text" [--source ] [--confidence high|medium|low] [--tags tag1,tag2]
Add a fact to an existing dossier.
Examples:
/dossier add person dr-klaus-richter "Gastroenterologista na Charité Berlin" --source "florayla/CONTEXT.md" --confidence high --tags role,affiliation
/dossier add mechanism cristais-de-otolitos "MUP da oferta Neuvelys — causa real do tinnitus" --source "neuvelys/CONTEXT.md" --confidence high --tags mup
/dossier search
Search across all dossiers (name, aliases, facts, relationships).
Examples:
/dossier search "Richter"
/dossier search "tinnitus"
/dossier search "Charité"
/dossier show
Display a dossier's full contents in readable format.
Examples:
/dossier show person dr-klaus-richter
/dossier show mechanism cristais-de-otolitos
/dossier merge
Merge two dossiers of same type. Source is archived after merge. Facts are deduplicated (Jaccard > 0.8). Contradictions are flagged (never auto-resolved).
Examples:
/dossier merge person dr-richter dr-klaus-richter
/dossier list [type]
List all dossiers, optionally filtered by type.
Examples:
/dossier list
/dossier list person
/dossier list mechanism
/dossier link [--note "context"]
Add a relationship between two dossiers.
Relationship types: works_at, uses, part_of, competes_with, created_by, related_to
Examples:
/dossier link person dr-klaus-richter florayla uses --note "Expert principal da oferta"
/dossier link person dr-klaus-richter charite-berlin works_at --note "Gastroenterologista"
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.
- 9d ago First seen · 113 lines · 0 tokens per session scan A f2036ce7a651
dossier is a command published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 889 tokens. 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 commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.