Borrowing it
Nothing to install: this file belongs to DanielPodolsky/ownyourcode. 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/DanielPodolsky/ownyourcode/main/.claude/skills/gates/ownership/SKILL.mdgit clone --depth 1 https://github.com/DanielPodolsky/ownyourcodeWrote 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/danielpodolsky/ownyourcode/ownership)<a href="https://agentmods.dev/skills/danielpodolsky/ownyourcode/ownership"><img src="https://agentmods.dev/badge/skills/danielpodolsky/ownyourcode/ownership/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/danielpodolsky/ownyourcode/ownership"><img src="https://agentmods.dev/badge/skills/danielpodolsky/ownyourcode/ownership.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.00893 |
| Opus 5.5 | $0.00015 | $0.00357 |
| Sonnet 5.5 | $0.00008 | $0.00179 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
ownership-gate 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 1mo 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gate 1: Ownership Verification
"If you can't explain it, you don't own it. And code you don't own will haunt you in interviews."
Purpose
This gate ensures the junior truly understands the code they've written. It's the only gate that can BLOCK task completion, because ownership is non-negotiable.
Gate Status
- BLOCKED — Junior cannot explain the code → Must review and understand before proceeding
- PASS — Junior demonstrates clear understanding
Gate Questions
Ask these questions in sequence. If the junior struggles significantly, mark as BLOCKED.
Question 1: Walk-Through
"Walk me through what this code does, step by step."
Looking for:
- Accurate description of the flow
- Understanding of data transformations
- Awareness of async operations
- Correct terminology
Red flags:
- "I'm not sure, I just copied this pattern"
- "The AI suggested this"
- Significant inaccuracies in description
Question 2: Why This Approach
"Why did you choose this approach? What alternatives did you consider?"
Looking for:
- Awareness of trade-offs
- Consideration of alternatives
- Reasoning about the decision
- Connection to requirements
Red flags:
- "It was the first thing that worked"
- "This is how it's done"
- No awareness of alternatives
Question 3: Change Scenario
"If the requirements changed to [specific scenario], what would you modify?"
Looking for:
- Understanding of which parts are flexible
- Awareness of dependencies
- Ability to reason about modifications
- Confidence in the architecture
Red flags:
- "I'd have to rewrite everything"
- Complete uncertainty about where to change
- Inability to identify the affected areas
Question 4: Edge Case
"What happens if [edge case specific to their code]?"
Looking for:
- Awareness of edge cases
- Understanding of failure modes
- Knowledge of error handling in the code
Red flags:
- "I didn't think about that"
- Complete surprise at the scenario
- No error handling for obvious cases
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.
- 1mo ago First seen · 149 lines · 38 tokens per session scan A 2a318fc0af83
ownership-gate is a skill published in the GitHub repository DanielPodolsky/ownyourcode (292 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 893 once invoked, about $0.0002 per session on Opus 5.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-code-review-swarm
Agent skill for code-review-swarm - invoke with $agent-code-review-swarm.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-review-patterns
Multi-dimensional code assessment across security, quality, performance, and maintainability with confidence-gated reporting (>=80%) and Router Contract generation.
code-review-pipeline
Multi-dimensional code review across correctness, security, performance, and maintainability with confidence-gated reporting and remediation loops.
security-review
Security vulnerability assessment identifying OWASP risks, injection vectors, authentication issues, and data exposure with severity classification.