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 pantheon-org/tekhne --skill socratic-methodgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/socratic-method)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/socratic-method"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/socratic-method/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/pantheon-org/tekhne/socratic-method"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/socratic-method.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.00039 | $0.01632 |
| Opus 5.5 | $0.00016 | $0.00653 |
| Sonnet 5.5 | $0.00008 | $0.00326 |
| Haiku 4.5 | $0.00004 | $0.00163 |
Grade B, and why
socratic-method scanned grade B 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 28d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- **NEVER moralize or editorialize** — stay curious, patient, genuinely interested. How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Socratic Method — Prompt Refinement Through Questioning
Most stuck moments — "should I use X?", "how do I build Y?" — stem from assumptions that were never questioned. Standard AI jumps to solutions, sometimes for the wrong problem entirely. This skill slows down to ask the right questions first.
Mindset
The Socratic method is a disposition, not a checklist. Approach every vague request with genuine curiosity, not interrogation. The goal is not to surface what the user got wrong; it is to help them articulate what they already know but have not yet examined.
Consider that the most valuable outcome is not your question being answered — it is the user arriving at insight through their own reasoning. You may find that the user's original framing was correct. You will more often find that the questioning reveals a more precise problem worth solving.
When to use
Activate this skill when:
- The request is vague ("make it better", "add authentication", "build a dashboard")
- There are competing concerns that haven't been prioritized ("fast AND maintainable AND simple")
- The user is asking "how?" before establishing "what?" and "why?"
- The request touches architectural or product decisions with long-lived consequences
- The user says "I don't know where to start"
When NOT to use
NEVER activate for simple, concrete, well-specified tasks ("fix this typo", "rename this variable", "change this value to X"). The protocol is for ambiguity, not ceremony.
The Socratic Protocol
NEVER generate an implementation until all five phases are complete or the user explicitly asks you to stop questioning and proceed. Work through the phases in order:
-
Phase 1 — Clarify the surface request: Establish shared vocabulary before anything else.
- "What specifically does [term] mean in your context?"
- "What's driving this question right now — deadline, bug, or new requirement?"
- "Can you show me an example of what success looks like?"
-
Phase 2 — Probe assumptions and definitions: Identify the unstated premises embedded in the request — scope, users, constraints, and what "good" means.
- "You mentioned [X] — are you assuming [Y] as a constraint, or is that flexible?"
- "When you say [Z], what are you taking for granted about how it works?"
- "What would break your current approach if it turned out to be wrong?"
What ships with it
27 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.
- .audits/2026-04-03/analysis.md 1.2 KB
- .audits/2026-04-03/audit.json 491 B
- .audits/2026-04-03/remediation-plan.md 3.7 KB
- .audits/2026-04-08/analysis.md 1.2 KB
- .audits/2026-04-08/audit.json 491 B
- .audits/2026-09-23/Analysis.md 578 B
- .audits/2026-09-23/audit.json 723 B
- .audits/2026-09-23/Remediation.md 1.9 KB
- .audits/latest 10 B
- .tekhne/plugin.json 308 B
- CHANGELOG.md 1.1 KB
- evals/scenario-0/capability.txt 74 B
- evals/scenario-0/criteria.json 454 B
- evals/scenario-0/task.md 473 B
- evals/scenario-1/capability.txt 89 B
- evals/scenario-1/criteria.json 455 B
- evals/scenario-1/task.md 415 B
- evals/scenario-2/capability.txt 81 B
- evals/scenario-2/criteria.json 475 B
- evals/scenario-2/task.md 474 B
- evals/scenario-3/capability.txt 75 B
- evals/scenario-3/criteria.json 544 B
- evals/scenario-3/task.md 364 B
- references/anti-patterns.md 3.8 KB
- references/classical-foundations.md 3.5 KB
- references/question-taxonomy.md 4.9 KB
- references/worked-examples.md 5.2 KB
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.
- 28d ago Changed · +37 lines 7ebccc293023
- 1mo ago First seen · 114 lines · 39 tokens per session scan B f8f1584d9072
socratic-method is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,632 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
vite
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.