guide

A guided coding command that helps you understand a task, find relevant references, and choose an implementation pattern. You write the production code yourself.

In plain words
What is it for?
Use it to clarify requirements, consult documentation, study examples, compare patterns, and work through implementation questions.
Why use it?
It gives structure when you are unsure how to approach a feature or coding problem, without hiding the learning process behind a finished solution.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/danielpodolsky/ownyourcode/guide
Clone the repo
git clone --depth 1 https://github.com/DanielPodolsky/ownyourcode

Made for: Claude Code.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,769 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00009 $0.01769
Opus 5 $0.00005 $0.00885
Sonnet 5 $0.00002 $0.00354
Haiku 4.5 $0.00001 $0.00177

Measured yesterday against content hash a30a45a7fe60, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

guide 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 yesterday.

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.

.claude/commands/own/guide.md · 275 lines

How it starts

The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/own:guide

⚠️ PLAN MODE WARNING: Toggle plan mode off before running this command (shift+tab). OwnYourCode commands don't work correctly with plan mode.

Get implementation guidance for your current task WITHOUT the AI writing code for you.

The Active Typist Rule

You provide guidance, patterns, and references. MAX 8 lines of example code. The human writes all production code.


Overview

This command helps the user implement a feature by:

  1. Understanding what they're trying to do
  2. Pointing to relevant documentation (Context7)
  3. Showing how production apps do it (Octocode)
  4. Providing patterns (not solutions)
  5. Asking clarifying questions

This command does NOT:

  • Write production code
  • Generate full implementations
  • Solve the problem for them

Execution Flow

Phase 1: Context Gathering

First, understand what they need help with:

Question: "What are you working on right now?"

Options:
1. A task from my active spec
   Description: Continue work on a planned feature

2. A specific coding problem
   Description: Need help with a particular implementation

3. Understanding a concept
   Description: Want to learn how something works

4. Reviewing my approach
   Description: Check if I'm on the right track

If they have an active spec, read it from the dashboard data:

  • Read ownyourcode/dashboard/dashboard-data.js (window.PROJECT); find the active phase (first with status !== "complete") and look at its tasks[] for current work
  • Reference the design decisions they made (the phase's design / spec)

Phase 2: The Socratic Approach

Before giving ANY guidance, ask:

"What have you tried so far?" "What's your current approach?" "What do you think the issue might be?"

This forces them to think before receiving help.


Phase 3: Research First (MANDATORY)

NEVER answer a technical question without research.

Use BOTH MCPs to gather intelligence:

Context7 — Official Documentation

Read the full file on GitHub · 275 lines

Changes

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.

  1. yesterday First seen · 275 lines · 9 tokens per session scan A a30a45a7fe60

Subscribe to this mod's changes

guide is a command published in the GitHub repository DanielPodolsky/ownyourcode (276 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 1,769 once invoked, about $0.0000 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.