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 eins78/agent-skills --skill dossiergit clone --depth 1 https://github.com/eins78/agent-skillsWrote 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/eins78/agent-skills/dossier)<a href="https://agentmods.dev/skills/eins78/agent-skills/dossier"><img src="https://agentmods.dev/badge/skills/eins78/agent-skills/dossier.svg" alt="Measured on agentmods" 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.00094 | $0.06150 |
| Opus 5 | $0.00047 | $0.03075 |
| Sonnet 5 | $0.00019 | $0.01230 |
| Haiku 4.5 | $0.00009 | $0.00615 |
Grade A, and why
dossier scanned grade A 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Source archival.** Capture each cited source to disk — `"${CLAUDE_SKILL_DIR}/scripts/archive-source.sh" <url> <citation-id> <dossier-folder>/sources`. **Assign the citation ID when you collect the URL, not when you wri How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dossier
Structured research producing cited, well-edited reports. Two genres: research dossiers that map the state of a topic so the reader draws their own conclusions, and decision dossiers that rank options and recommend one. Optional decision ballots. Works for any domain — tech, travel, health, policy, finance, art.
Pick the genre before researching — it changes every stage below. Getting it wrong is the most expensive error this skill can make: it is invisible until delivery, and it cannot be patched by editing, because the two genres want different documents built from the same facts.
Workflow: SCOPE → GATHER → EVALUATE → SYNTHESIZE → REVIEW → DELIVER
0. Preflight — verify the request is actionable, and settle the genre
Before starting research, confirm all three:
- Specific — what to investigate is bounded: a named topic, a concrete comparison, or a clear question. "Look into the X space generically" fails this.
- Unambiguous — contested terms are defined by context. If the request uses a word with multiple plausible meanings and context doesn't resolve which, flag it.
- Well-understood — you can state the objective back to the operator in 1–2 sentences without hedging. If you'd have to pad with "I think you mean…" or "depending on what you want from this…", you don't understand it yet.
If one or more checks fail, ask before starting. A dossier built on unclear objectives wastes more research time than the clarifying turn costs. Batch questions; offer choices where reasonable; skip the obvious.
Then settle the genre — a fourth, independent check:
- Genre — does the reader want to learn the state of a topic and conclude for themselves, or to be handed a ranked recommendation? Infer it when the request makes it obvious; ask when it doesn't.
| Request | Genre | Why |
|---|---|---|
| "brief me on the CMS MCP landscape" | Research | Asks about the world |
| "which CMS should we standardise on?" | Decision | Asks for a choice |
| "research X and tell me if we should do it" | Research + assessment | Explicitly both |
| "evaluate this pitch" | Ask | Evaluate reads both ways: "tell me if it's good" and "tell me about this space so I can judge" |
| "what are my options for X?" | Ask | Could be a survey of the field or a shortlist to pick from |
What ships with it
8 files 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.
- 7d ago First seen · 240 lines · 94 tokens per session scan A 70ac7ab2fc36
dossier is a skill published in the GitHub repository eins78/agent-skills (2 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 6,150 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
xiaohongshu-search-full
Search Xiaohongshu (XHS / RedNote) notes by keyword with full field extraction including body text, topics/tags, image list URLs, video stream URL, publish timestamp, and all engagement stats (likes, collects, comments, shares). Supports all page filter options: sort order (general, latest, most liked, most commented…
x-tweet-by-conversation
Collects every tweet in an X (Twitter) conversation thread given a conversation id (root tweet id) — the focal tweet plus all replies, sub-replies, and quote chains — and returns normalized per-tweet data with text, author, engagement counts, media, hashtags, mentions, inreplyto mapping, and cursor for pagination. Use…
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
muapi-media-editing
Edit and enhance images and videos with AI via muapi.ai — prompt-based editing, upscaling, background removal, face swap, lipsync, video effects, and more.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…