context

context is a command for Claude Code from HigorAlves/orc. It costs 20 tokens per session (839 once invoked), scanned A, original, MIT.

A command for creating or updating a repository's project-context file, which records the rules and facts coding agents must follow before changing code. It can generate, display, refresh, or append a rule to that file.

In plain words
What is it for?
Use it to derive a project's stack, test and build commands, coding conventions, and binding rules from its source, configuration, and CI files.
Why use it?
It keeps project-specific conventions, commands, and known pitfalls in one committed place that survives across branches and agent sessions. This reduces the chance that agents guess the repository's rules incorrectly.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the orc plugin — 88 skills, 30 commands, 14 agents, 6 hooks shipped together

Good fit Use it to derive a project's stack, test and build commands, coding conventions, and binding rules from its source, configuration, and CI files.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/higoralves/orc/context
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.

Clone the repo
git clone --depth 1 https://github.com/HigorAlves/orc

Made for: Claude Code.

Or install orc, the plugin that ships this one along with the rest of its 88 skills, 30 commands, 14 agents, 6 hooks.

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 context

README.md
[![agentmods](https://agentmods.dev/badge/commands/higoralves/orc/context/github.svg)](https://agentmods.dev/commands/higoralves/orc/context)
Your own site
<a href="https://agentmods.dev/commands/higoralves/orc/context"><img src="https://agentmods.dev/badge/commands/higoralves/orc/context/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.

agentmods 80×15 button for context

Your own site · 80×15
<a href="https://agentmods.dev/commands/higoralves/orc/context"><img src="https://agentmods.dev/badge/commands/higoralves/orc/context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 839 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.
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.00020 $0.00839
Opus 5.5 $0.00008 $0.00336
Sonnet 5.5 $0.00004 $0.00168
Haiku 4.5 $0.00002 $0.00084

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

Security

Grade A, and why

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

orc/commands/context.md · 87 lines

How it starts

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

/orc:context

Maintain docs/agents/project-context.md, the committed file that survives every branch. Contract, sections, cap and line rubric live in orc:project-context.

Arguments

  • generate (default): interview the repo and write the file. Refuses when the file exists.
  • show: print the file and its size against the cap. Read-only.
  • refresh: re-derive the file and gate on the diff.
  • add-rule "<text>": append one rule. /orc:retro calls this path.
  • --section <name>: with add-rule, the target section.

Preconditions

  • Invoke orc:project-context first.
  • Target path is docs/agents/project-context.md in the current repo.
  • A missing file is not an error for show: say so and offer generate.

Workflow

generate

  1. Prime discovery per orc:code-discovery; fall back to Glob and Grep silently.
  2. Derive the stack from manifests, lockfiles and CI runtimes.
  3. Derive the test, lint, typecheck and build commands from CI scripts, Makefile and package scripts.
  4. Derive conventions from the real source tree. The code wins over the README.
  5. Derive binding rules from CI gate scripts, hooks and CONTRIBUTING.md.
  6. Drop every line that fails the rubric in the FORMAT.md reference of orc:project-context.
  7. Write the cap in the file header: 150 lines / 6 KB.
  8. Print the gate below, then the full draft.
  9. Write the file only after approval.
  10. Print the size line.

⛔ Gate — project context

lines against the 150-line cap, path docs/agents/project-context.md.

Ask with AskUserQuestion: Write it, Trim first, Cancel. This gate asks at every autopilot level. The file steers every later agent.

refresh

  1. Read the existing file.
  2. Keep every <!-- human --> line and everything under ## Notes untouched.
  3. Re-derive the rest as in generate steps 1 to 6.
  4. Say "project-context.md is current" and stop when nothing differs.
  5. Gate on the diff with AskUserQuestion: accept all, pick hunks, cancel.
  6. Write the file and print the size line.

Read the full file on GitHub · 87 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 · 87 lines · 20 tokens per session scan A e0428834db08

Subscribe to this mod's changes

context is a command published in the GitHub repository HigorAlves/orc (7 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 839 once invoked, about $0.0001 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-10-24.