prime

prime is a command for Claude Code from TheSmokeDev/taskchad-os. It costs 6 tokens per session (365 once invoked), scanned A, original, MIT.

A command for building a broad understanding of a codebase by reading its files, documentation, structure, configuration, important entry points, and recent Git history.

In plain words
What is it for?
Use it at the start of work on an unfamiliar repository to identify its purpose, technologies, architecture, important files, and current state.
Why use it?
It gives the agent project context before making changes, reducing the chance of overlooking conventions or key dependencies.

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/thesmokedev/taskchad-os/prime
Clone the repo
git clone --depth 1 https://github.com/TheSmokeDev/taskchad-os

Made for: Claude Code.

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 prime

README.md
[![agentmods](https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/prime.svg)](https://agentmods.dev/commands/thesmokedev/taskchad-os/prime)
Your own site
<a href="https://agentmods.dev/commands/thesmokedev/taskchad-os/prime"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/prime.svg" alt="Measured on agentmods" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 365 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.1 $0.00006 $0.00365
Opus 5 $0.00003 $0.00182
Sonnet 5 $0.00001 $0.00073
Haiku 4.5 $0.00001 $0.00036

Measured 5d ago against content hash 229f59045da9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

prime 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 5d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • prime — 100% identical, 0 lines differ
.claude/commands/core_piv_loop/prime.md · 74 lines

What it actually says

Prime: Load Project Context

Objective

Build comprehensive understanding of the codebase by analyzing structure, documentation, and key files.

Process

1. Analyze Project Structure

List all tracked files: !git ls-files

Show directory structure: On Linux, run: tree -L 3 -I 'node_modules|__pycache__|.git|dist|build'

2. Read Core Documentation

  • Read CLAUDE.md or similar global rules file
  • Read README files at project root and major directories
  • Read any architecture documentation

3. Identify Key Files

Based on the structure, identify and read:

  • Main entry points (main.py, index.ts, app.py, etc.)
  • Core configuration files (pyproject.toml, package.json, tsconfig.json)
  • Key model/schema definitions
  • Important service or controller files

4. Understand Current State

Check recent activity: !git log -10 --oneline

Check current branch and status: !git status

Output Report

Provide a concise summary covering:

Project Overview

  • Purpose and type of application
  • Primary technologies and frameworks
  • Current version/state

Architecture

  • Overall structure and organization
  • Key architectural patterns identified
  • Important directories and their purposes

Tech Stack

  • Languages and versions
  • Frameworks and major libraries
  • Build tools and package managers
  • Testing frameworks

Core Principles

  • Code style and conventions observed
  • Documentation standards
  • Testing approach

Current State

  • Active branch
  • Recent changes or development focus
  • Any immediate observations or concerns

Make this summary easy to scan - use bullet points and clear headers.

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. 5d ago First seen · 74 lines · 6 tokens per session scan A 229f59045da9

Subscribe to this mod's changes

prime is a command published in the GitHub repository TheSmokeDev/taskchad-os (23 stars, last pushed 13d ago), licensed MIT. It adds 6 tokens to every session and 365 once invoked, about $0.0000 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.