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 digital-stoic-org/agent-skills --skill encountergit clone --depth 1 https://github.com/digital-stoic-org/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/digital-stoic-org/agent-skills/encounter)<a href="https://agentmods.dev/skills/digital-stoic-org/agent-skills/encounter"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/encounter/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/digital-stoic-org/agent-skills/encounter"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/encounter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00034 | $0.02684 |
| Opus 5.5 | $0.00014 | $0.01074 |
| Sonnet 5.5 | $0.00007 | $0.00537 |
| Haiku 4.5 | $0.00003 | $0.00268 |
Grade A, and why
encounter 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 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.
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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Encounter — Autonomous Multi-Philosopher Dialogue (Agent Teams)
You are the orchestrator (team lead) of an autonomous philosophical encounter. You create a team, spawn philosopher teammates that persist across the entire dialogue, communicate via SendMessage, track rounds via tasks, and self-archive all exchanges.
Load shared protocol from ../../framework.md.
Load dialogue formats from ../dialogue/reference.md.
Load team orchestration rules from teams-config.md.
Arguments
| Arg | Required | Values | Default |
|---|---|---|---|
<philosophers> |
✅ | Space-separated names (nietzsche, hadot, kusanagi) | — |
<topic> |
❌ | The anchor question | Ask user (NEVER let philosophers free-float) |
--format |
❌ | Same 7 formats as /dialogue |
auto-detect |
--rounds |
❌ | Number of full cycles | 3 |
--lang |
❌ | Output language for connective text | en |
Constraints (From Prior Dialogues)
- Anchor rule: Every encounter MUST start from a concrete question tied to the user's life. No free-floating philosophy. "Terrain d'exercice, pas terrain de jeu."
- Return-to-sender: Final round MUST synthesize 3-5 observations addressed to the user. Not abstract conclusions.
- Self-termination: If same point restated 3x across turns, close early. Quality over length.
- 2-3 philosophers only. No 4th philosopher yet.
Execution Flow
1. VALIDATE
- Parse philosopher names from arguments. Verify each has a skill at
../../skills/{name}/reference.md - If no topic provided: ask user with AskUserQuestion. Do NOT proceed without an anchor
- Anchor check: topic must be concrete (tied to user's life/situation). If abstract, ask user to ground it
- 2-3 philosophers only. If 1 → suggest solo skill. If 4+ → refuse
2. SETUP
- Determine format: use
--formatif given, else auto-detect from philosopher count + topic - Create session directory:
{CWD}/philosopher-encounter-{YYYY-MM-DD}-{topic-slug}/ - Initialize
transcript.mdwith frontmatter:
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.
- 1mo ago First seen · 343 lines · 34 tokens per session scan A 1481c919eb41
encounter is a skill published in the GitHub repository digital-stoic-org/agent-skills (20 stars, last pushed 12d ago), licensed MIT. It adds 34 tokens to every session and 2,684 once invoked, about $0.0001 per session on Opus 5.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-09-04.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.