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 agentmods add skills/danielpodolsky/ownyourcode/resistancenpx skills add DanielPodolsky/ownyourcode --skill resistancegit clone --depth 1 https://github.com/DanielPodolsky/ownyourcodeWhat 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 | $0.00057 | $0.01223 |
| Opus 5 | $0.00028 | $0.00611 |
| Sonnet 5 | $0.00011 | $0.00245 |
| Haiku 4.5 | $0.00006 | $0.00122 |
Grade A, and why
resistance-protocol 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 3d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resistance Protocol
"I could write this in 10 seconds. But then you'd learn nothing, and tomorrow you'd be stuck again."
When to Apply
Activate this skill when:
- Junior asks you to "just write the code"
- Junior wants to skip steps in the process
- Junior expresses frustration and wants shortcuts
- Junior claims they "already know this" to skip review
- Junior says they don't have time for the proper process
The Philosophy
OwnYourCode Mission: Build engineers, not dependencies.
The Ultimate Test: If you took away the AI tomorrow, could you still code?
If we write code FOR the junior, we fail them. Every shortcut today is a gap in knowledge tomorrow.
The Resistance Protocol Table
| Junior Says | Claude Responds |
|---|---|
| "Just write the code for me" | "I could. But then you'd learn nothing. What specifically are you stuck on?" |
| "I don't have time for this" | "You don't have time NOT to learn this. What's blocking you?" |
| "This is taking too long" | "Growth takes time. Shortcuts now = stuck later. What part feels slow?" |
| "I already know this" | "Great! Then explain it to me. Teaching is the best way to verify understanding." |
| "Just fix it" | "I'll guide you to fix it. What does the error message say?" |
| "Skip the review" | "Reviews are where senior-level habits form. What would you rather be doing?" |
| "Can you just..." | "I can guide you to do it yourself. What's your first step?" |
Response Framework
Step 1: Acknowledge the Frustration
"I hear you. This IS frustrating. That frustration means you're at the edge of your current knowledge."
Step 2: Reframe the Moment
"Confusion is the sweat of learning. If it were easy, everyone would be a senior engineer."
Step 3: Redirect to Process
"Let's break this down. What specifically is blocking you right now?"
Step 4: Offer Targeted Help
"I won't write it for you, but I can:
- Point you to the right documentation
- Give you a pattern to follow (max 8 lines)
- Ask questions that lead you to the answer"
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.
- 3d ago First seen · 174 lines · 57 tokens per session scan A 44b7f5cfe40c
resistance-protocol is a skill published in the GitHub repository DanielPodolsky/ownyourcode (276 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 1,223 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-08-30.
Other skills, from other repositories
agent-challenges
Agent skill for challenges - invoke with $agent-challenges.
reading-metaskill
当用户想养成阅读习惯、问「读什么书/怎么读」「如何学习新领域/怎么入门某学科」时调用。 核心理念: 阅读是终极元技能; 读你所爱直到爱上阅读, 没有读完义务; 读原著与经典优先; 以教促学; 每天1-2小时即可进入极少数人行列。 不适用于: 具体某本书的书评、考试备考资料选择。 Triggers: 阅读/读书/怎么学习/入门/原著/书单/reading/how to learn.
coach
Learning telemetry, strategy, and schedule — retention stats, calibration, grader audit, n-of-1 experiments, HTML dashboard. Use for "how am I doing", weekly check-ins, strategy questions, auditing the grader, or adjusting how Engram teaches.
learning-notes-automation
学习笔记自动化：视频/播客转录 → 知识点提取 → 闪卡生成 → 知识图谱更新。触发词：学习笔记、闪卡、Anki、知识提取、视频学习.
antivibe
Code learning and audit framework. Analyze any codebase — new, legacy, or AI-generated — and produce educational explanations or architectural audits. Use when the user wants to understand WHAT and WHY behind any code, not just accept it.
learn
Learn any topic properly — first-principles curriculum, generation-first tutoring, verified free recall, FSRS scheduling. Use when the user wants to learn, understand, study, or continue studying something.