claude-code — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited claude-code (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
What it is: Claude Code is Anthropic's terminal-first agent harness — a CLI and runtime that drives a frontier Claude model (Opus 4.8 as of mid-2026) through a real codebase with a native extensibility stack: skills, hooks, subagents, MCP, plan mode, background tasks, and slash commands.
Mental model: The harness is the body; the model is the brain. The model decides what to do; the harness decides what the model is allowed to do and how its actions are gated, rendered, parallelized, and persisted. Choosing Claude Code is choosing that body — its permission model, its extensibility layers, and its context budget — not just the underlying model.
Why it exists: A frontier model alone cannot safely operate a codebase. The harness supplies the missing scaffolding — typed tool surfaces the host can gate, lifecycle hooks for automation and security, isolated subagent context windows, on-demand skill loading, and a plan-before-act mode — so a long-horizon coding task can run autonomously without losing control or context.
What it is NOT: It is not the Anthropic API or SDK (that is application code you write), not the Claude model itself (the model is swappable inside the harness), and not a generic "agent framework" you assemble — it is one specific, opinionated harness with a fixed protocol.
Adjacent concepts: the Codex CLI (the GPT-running rival harness), OpenCode (the provider-agnostic open-source harness), the Claude API (the SDK surface for building your own harness), and generic autonomous-loop patterns (the topology underneath any harness).
One-line analogy: Picking a harness is like picking the cockpit, not the pilot — the same pilot flies differently depending on which instruments, autopilot, and safety interlocks the cockpit gives them.
Common misconception: That "Claude Code" and "Claude" are the same choice. They are two orthogonal decisions: which harness (Claude Code vs Codex vs OpenCode) and which model runs inside it. Conflating them leads to picking a harness for a model strength it does not own, or vice versa.
run_in_background), slash commandsclaude-api), Claude-vs-GPT model routing (gpt-5-5), generic agent-loop topology (autonomous-loop-patterns)Reach for Claude Code when the task wants its native extensibility stack or its plan-then-act control, and the work lives in a real repo:
| Want this | Why Claude Code fits |
|---|---|
| On-demand, reusable expertise the agent loads only when relevant | Skills — progressive disclosure via the Skill tool; the description sits in context, the body loads on demand |
| Deterministic automation or a security gate around the agent's actions | Hooks — use lifecycle hook points such as PreToolUse for gates that must run before tools execute; verify the current hook event list before depending on a specific count |
| Parallel or isolated sub-work without polluting the main context | Subagents — each runs in its own context window; only a summary returns |
| Investigate-and-propose before any edit lands | Plan mode — read-only planning phase, then execute on approval |
| Kick off a long shell job and keep working | Background tasks — run_in_background on the Bash tool; notified on completion |
| A very large codebase or multi-day project held in one window | 1M context on the Opus tier (no long-context premium on the Opus model), with cross-session context carry |
| Anthropic-first reasoning quality on architecture and large-codebase work | Runs Opus; treat current benchmark claims as dated routing evidence and re-check them before making a model-choice decision |
Choose a different harness when its differentiator is the point of the task — see the boundary table below.
| Layer | What it gives you | When it earns its keep |
|---|---|---|
| Skills | Named instruction bundles, loaded on demand via the Skill tool | Recurring domain knowledge the base prompt should not always carry |
| Hooks | Lifecycle automation at 25 points (e.g. PreToolUse) | Security gates, formatters, telemetry, "always do X before/after Y" |
| Subagents | Isolated-context specialized instances | Fan-out, noisy investigation, parallel independent workstreams |
| MCP | External tool/data connectors | Capabilities with no native CLI — but prefer a CLI when one exists |
| Plan mode | Read-only investigate-then-propose phase | High-stakes or unfamiliar code where a wrong edit is expensive |
| Background tasks | run_in_background Bash jobs with completion notification | Long builds, test suites, dev servers that should not block the loop |
| Slash commands | User-typed /command workflows from .claude/commands/ | Repeatable operator workflows |
| 1M-context Opus | The model's full window inside the harness | Large repos, long sessions, multi-day projects |
Strengths
Weaknesses / watch-outs
git-commit permission propagation in this workspace (commit-deliverable work prefers foreground dispatch).Harness choice is an axis people routinely collapse into model choice, and that collapse is where bad decisions come from. The opinionated stance here is that you pick the body on the strength it actually owns — the extensibility protocol, the control surface, the context budget — not on a model strength that travels with the model regardless of harness. The corollary is anti-tribal: the best harness for a given task is not always the one whose model you prefer. A task that lives in terminal-command iteration may belong on the rival even when you favour Anthropic's reasoning; a non-Anthropic-model lane forces a provider-agnostic harness no matter how good the native extensibility is. The skill is therefore deliberately written to route work away from itself when a rival's differentiator is the point of the task — a harness skill that never says "use the other one" is a sales pitch, not a routing contract. And because the harness ships features fast, the discipline is to treat every version-specific capability claim as perishable: verify against current docs, never quote a hook count or flag from memory.
Before concluding "run this in Claude Code," confirm:
gpt-5-5) or the SDK call (→ claude-api).codex; non-Anthropic-model routing → OpenCode). If one is, route there.Instead of claude-code | Use | Why |
|---|---|---|
| Writing code that calls the Anthropic Messages API / SDK | claude-api | That is application code, not a harness-selection decision |
| Deciding whether GPT-5.5 or Claude should do the task | gpt-5-5 | That is a MODEL-routing decision, orthogonal to the harness |
Choosing the resumable-session, exec-piping GPT harness | codex | When the task wants Codex's specific differentiators |
| Designing a generic resumable/supervised agent loop | autonomous-loop-patterns | That is loop topology, below any specific harness |
references/model-facts.md — verified capability + model facts (Opus 4.8 era, 2026-06-08) with sourcescodex and gpt-5-5 — the rival-harness and model-routing decisions this skill defers to~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.