status

A read-only project status command that gathers progress, active work, learning records, recent changes, and—when enabled—career material such as interview stories and resume bullets.

In plain words
What is it for?
Use it to check roadmap progress, see current tasks, review recent commits, track documented learning, and view collected career material.
Why use it?
It brings key project information into one report, so you do not have to inspect several files and folders yourself.

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/status
Clone the repo
git clone --depth 1 https://github.com/DanielPodolsky/ownyourcode

Made for: Claude Code.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,274 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.00015 $0.02274
Opus 5 $0.00008 $0.01137
Sonnet 5 $0.00003 $0.00455
Haiku 4.5 $0.00002 $0.00227

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

Security

Grade A, and why

status 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/status.md · 317 lines

How it starts

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

/own:status

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

Get a comprehensive status report on project progress and learning growth.

Overview

This command provides:

  1. Roadmap Progress — Where you are in the project
  2. Active Specs — Current work in progress
  3. Learning Stats — Skills and patterns documented
  4. Recent Activity — Last commits and changes
  5. Career Stats — Interview stories and resume bullets collected (if enabled)

Profile-Aware Behavior: Check .claude/ownyourcode-manifest.json for profile.settings.career_focus:

  • If "full-extraction" or "tips-only" → Show Career Stats section
  • If "none"Hide Career Stats section entirely

Execution Flow

Step 1: Gather Data

Read project files to compile status. This step is read-only/own:status never writes to dashboard-data.js.

ownyourcode/dashboard/dashboard-data.js — window.PROJECT: roadmap, specs, tasks, DoD (the SDD source of truth)
ownyourcode/career/stories/   — Interview stories
learning/LEARNING_REGISTRY.md — Learning flywheel data
.claude/skills/learned/       — Auto-generated skills

From window.PROJECT, compute (do not store — these are derived):

  • Roadmap progress = phases grouped by status (roadmap-only / specced / complete)
  • Active phase = first phase with status !== "complete"
  • Per-phase task progress = tasks.filter(t => t.done).length / tasks.length
  • DoD progress = dod.filter(d => d.done).length / dod.length

Also check git activity:

git log --oneline -10 --since="1 week ago"

Step 2: Generate Status Report

Roadmap Progress

Derive each phase's line from its status and (if specced) its task progress:

## Roadmap Progress

Phase 1: Foundation     ██████████ complete
Phase 2: Logging        █████░░░░░ specced · 3/5 tasks
Phase 3: Visualization  ░░░░░░░░░░ roadmap-only

Overall: 1 complete · 1 specced · 1 planned  (of 3 phases)

Read the full file on GitHub · 317 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 · 317 lines · 15 tokens per session scan A d30ca662ebe5

Subscribe to this mod's changes

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