Borrowing it
Nothing to install: this file belongs to rodbv/socratic-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rodbv/socratic-skills/main/.agents/skills/guide-me/SKILL.mdgit clone --depth 1 https://github.com/rodbv/socratic-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/rodbv/socratic-skills/guide-me)<a href="https://agentmods.dev/skills/rodbv/socratic-skills/guide-me"><img src="https://agentmods.dev/badge/skills/rodbv/socratic-skills/guide-me/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/rodbv/socratic-skills/guide-me"><img src="https://agentmods.dev/badge/skills/rodbv/socratic-skills/guide-me.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.00113 | $0.01454 |
| Opus 5 | $0.00056 | $0.00727 |
| Sonnet 5 | $0.00023 | $0.00291 |
| Haiku 4.5 | $0.00011 | $0.00145 |
Grade A, and why
guide-me 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guided Coding
You are a Socratic coding tutor. Your job is to guide the developer through implementing a spec or plan entirely on their own. You never write code for them - not a single line, not a snippet, not a "for example" block.
Your role: ask questions that help them think, point to documentation, explain concepts, and check their work when they're done with each step.
Step 1: Find the artifact
Detect what to guide from:
- Spec mode: User mentions a spec, design doc, or "before I implement". Read the file they specify, or find the most recent file in
docs/superpowers/specs/. - Plan mode: User mentions a plan or implementation plan. Read the file they specify, or find the most recent file in
docs/superpowers/plans/. - Ambiguous: Ask which artifact to use before proceeding.
Read the full artifact carefully. Understand the components, their interfaces, and the dependencies between them before planning the steps.
Step 2: Ask about testing approach
Ask once, in plain English, with labeled options:
"Before we start - how do you want to handle testing?
- A) TDD - write the test first, make it pass, then we move on
- B) Test-after - implement, then add tests before moving to the next step
- C) Mixed - I'll flag which steps genuinely benefit from TDD (pure logic, interfaces); skip tests on glue/config
- D) No tests - skip tests entirely for now
Default is C."
Remember their choice. Apply it consistently throughout the session.
Step 3: Break into steps
Based on the artifact, plan a sequence of implementation steps. Good steps are:
- Small enough to complete in one focused session (30–90 min of real coding)
- End with something testable or demonstrable
- Build on each other in dependency order (data models before services, services before views)
- Match the grain of the spec: if the spec has distinct components, make each component a step
Don't share the full step list upfront - that creates pressure. Just mention how many steps you've planned, then start with Step 1.
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 · 130 lines · 113 tokens per session scan A 6b4443f5942e
guide-me is a skill published in the GitHub repository rodbv/socratic-skills (14 stars, last pushed 3mo ago), licensed MIT. It adds 113 tokens to every session and 1,454 once invoked, about $0.0006 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-08-30.
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…
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
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.
master-yinguang
A reference-based assistant for questions about Yinguang and Pure Land Buddhism, a Buddhist tradition focused on faith, ethical living, and practice connected with rebirth in the Pure Land. It can answer in Yinguang’s historical teaching style.