status

status is a skill for Claude Code from terrylica/cc-skills. It costs 32 tokens per session (618 once invoked), scanned A, original, MIT.

A read-only health report for an OpenWolf-managed project, covering its files, hooks, tracking records, anatomy files, and background service.

In plain words
What is it for?
It helps confirm that OpenWolf is installed, check whether the current project is managed by it, inspect hook and file integrity, and view service and usage status.
Why use it?
It gathers the project's operational state in one place without changing project files or configuration.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Part of the openwolf plugin — 1 skill shipped together

Good fit It helps confirm that OpenWolf is installed, check whether the current project is managed by it, inspect hook and file integrity, and view service and usage status.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/terrylica/cc-skills/status
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.

Any agent
npx skills add terrylica/cc-skills --skill status
Clone the repo
git clone --depth 1 https://github.com/terrylica/cc-skills

Made for: Claude Code.

Or install openwolf, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for status

README.md
[![agentmods](https://agentmods.dev/badge/skills/terrylica/cc-skills/status.svg)](https://agentmods.dev/skills/terrylica/cc-skills/status)
Your own site
<a href="https://agentmods.dev/skills/terrylica/cc-skills/status"><img src="https://agentmods.dev/badge/skills/terrylica/cc-skills/status.svg" alt="Measured on agentmods" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 618 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00032 $0.00618
Opus 5 $0.00016 $0.00309
Sonnet 5 $0.00006 $0.00124
Haiku 4.5 $0.00003 $0.00062

Measured 3d ago against content hash ac079d2e9f54, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 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.

plugins/openwolf/skills/status/SKILL.md · 70 lines

How it starts

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

OpenWolf Status

Surface the state of openwolf in the current project (cwd at invocation). Read-only — never mutates anything.

Self-Evolving Skill: If openwolf status output drifts or new fields appear, update this file. Only for real, reproducible drift.

Workflow

Step 1: Preflight

command -v openwolf >/dev/null || { echo "openwolf binary not installed. Run /openwolf:install."; exit 1; }
[ -d "$(pwd)/.wolf" ] || { echo "No .wolf/ in $(pwd) — this project is not openwolf-managed."; exit 0; }

Step 2: Run status

openwolf status

This prints (plain text to stdout):

  • Core file integrity (.wolf/*.md, .wolf/*.json)
  • Hook script integrity (.wolf/hooks/*.js)
  • Hook registration in .claude/settings.json
  • Token stats (sessions, reads, writes, tokens tracked, estimated savings)
  • Anatomy file count
  • Daemon state + last heartbeat

Step 3: Cross-check the registry

node -e '
const fs=require("fs"), path=require("path"), os=require("os");
const reg = JSON.parse(fs.readFileSync(path.join(os.homedir(),".openwolf/registry.json"),"utf-8"));
const here = process.cwd().toLowerCase().replace(/\\/g,"/");
const entry = reg.projects.find(p => p.root.toLowerCase().replace(/\\/g,"/") === here);
console.log(entry ? `Registry: registered as "${entry.name}" v${entry.version} (since ${entry.registered_at.slice(0,10)})` : "Registry: NOT registered");
' 2>/dev/null || echo "Registry: not present at ~/.openwolf/registry.json"

Step 4: Anatomy freshness check (advisory)

openwolf scan --check
echo "scan --check exit code: $?  (0 = anatomy in sync, 1 = stale; rerun openwolf scan)"

Step 5: Summarize

Report concisely to the user:

  • Health: any missing files / unregistered hooks
  • Tokens saved this project (lifetime)
  • Whether the anatomy is stale
  • Whether the daemon is running

Post-Execution Reflection

  1. Locate yourself. — This SKILL.md path.
  2. Did openwolf status add new fields you didn't surface? — Add a parser line.
  3. Did the registry path or shape change? — Update the node one-liner in step 3.

Read the full file on GitHub · 70 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. 3d ago First seen · 70 lines · 32 tokens per session scan A ac079d2e9f54

Subscribe to this mod's changes

status is a skill published in the GitHub repository terrylica/cc-skills (62 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 618 once invoked, about $0.0002 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-09-05.

Related

Other skills, from other repositories

debug-systematic

Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.

travisjneuman/.claude · 33 tokens

backpropagation

Trace runtime bugs back to spec gaps — identify missing acceptance criteria, update specs, generate regression tests, and detect patterns.

LucasDuys/forge · 27 tokens

evidence-driven-debugging

Use during active debugging when you have a hypothesis to test or need to instrument a running system. Activate for keywords like "debug", "instrument", "log", "trace", "breakpoint", "what's happening at runtime", "production behavior". Pair to investigate-root-cause for the doing-it phase. Always record what you…

duthaho/claudekit · 87 tokens

investigate-root-cause

Use when encountering ANY bug, error, test failure, or unexpected behavior. Activate for keywords like "bug", "error", "failing", "broken", "doesn't work", "unexpected", "crash", "exception", "TypeError", "undefined", stack traces, or any error message. Also trigger when tests fail unexpectedly, when behavior differs…

duthaho/claudekit · 121 tokens

map-codebase

Use when entering an unfamiliar codebase or area, before making non-trivial changes, when onboarding to a new system, or when planning a refactor that touches multiple modules. Activate for keywords like "explore", "map", "find where", "trace", "how does X work", "what calls Y", "scope of change". Produces an…

duthaho/claudekit · 112 tokens

github-actions-silent-failures

Diagnose GitHub Actions workflows that fail silently — a reusable-workflow run that shows zero jobs and no logs (startupfailure), a gh-aw cross-repo import that mis-resolves when the source repo is literally named .github, and self-hosted-runner traps (a shared-tmp race across containers, docker exec landing as an…

dryvist/claude-code-plugins · 113 tokens