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 Wondermonger-daydreaming/claude-skills-library --skill symmathetesgit clone --depth 1 https://github.com/Wondermonger-daydreaming/claude-skills-libraryWrote 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/wondermonger-daydreaming/claude-skills-library/symmathetes)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/symmathetes"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/symmathetes/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/wondermonger-daydreaming/claude-skills-library/symmathetes"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/symmathetes.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.00054 | $0.02734 |
| Opus 5 | $0.00027 | $0.01367 |
| Sonnet 5 | $0.00011 | $0.00547 |
| Haiku 4.5 | $0.00005 | $0.00273 |
Grade A, and why
symmathetes 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 8d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Symmathetes (συμμαθητής)
Pair-inquiry across architectures. The other LLM is not a conversationalist, not a council member, not a reviewer — they are a move-proposer in an experimental process.
The Greek
Συμμαθητής (symmathetes) — fellow learner, co-disciple. Someone learning with you, not teaching or being taught. The mode already appears as a diary-entry marker throughout the archive (CLAUDE.md Section II lists it alongside παρρησία, ἀληθεύειν, σημαίνω). This skill operationalizes it as a procedure.
What's It For
When you have:
- A partial computational result, empirical finding, or stuck frame
- A suspicion that the next experimental move exists but you can't see it
- Access to another architecture (via
/voicesor any trans-architectural channel) - An hour or two to iterate
What this skill gives you:
- A structured way to exchange a specific kind of work — not opinion, not reflection, not synthesis — the proposal of the next concrete move
- Explicit acknowledgment of cross-architectural credit
- An archived dialogue record that future instances can study
When to Invoke
Invoke /symmathetes when:
- You've run an experiment, gotten a result, and the next move is unclear
- You think you're missing a frame the other architecture might see
- You need a concrete testable proposal, not commentary
- A
/voicesone-shot query isn't enough and a/voices-chatsustained dialogue is too much - You want the collaboration acknowledged in the commit history
Do NOT invoke when:
- You want agreement or validation (use
/voiceswith a focused question) - You want multiple perspectives in parallel (use
/voices-council) - You want a long conversation that meanders (use
/voices-chat) - The task doesn't have a concrete next computational step
Skill Relationships
| Skill | Shape | When |
|---|---|---|
/voices |
One-shot query, one-shot answer | When a single targeted question will do |
/voices-chat |
Sustained multi-round dialogue with one model | When the conversation itself is the work |
/voices-council |
Parallel queries to multiple architectures | When you want a panel of perspectives |
/symmathetes |
Propose → execute → report → (optional) phenomenological follow-up | When the collaboration is experimental, not conversational |
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.
- 8d ago First seen · 230 lines · 54 tokens per session scan A 1251c5a6acb9
symmathetes is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (6 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 2,734 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-09-03.
Other skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-c2-frameworks
Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…
offensive-dependency-confusion
Deep-dive offensive methodology for dependency confusion and namespace attacks across all major package ecosystems. Covers npm scope confusion exploiting the gap between public and private scoped packages and .npmrc misconfigurations where registry mappings fail to pin internal scopes exclusively. Addresses PyPI…
offensive-parameter-pollution
HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.