Project Context Setup

What it does

When your agent uses it

• : set up project context
• Configure agent docs
• Create CONTEXT.md
• Setup agent workflow

Example prompts

• “set up project context”
• “configure agent docs”
• “create CONTEXT.md”
• “/project-context-setup”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

1. 1Explore
2. 2Choose Setup Values
3. 3Write Context Files
4. 4Add Agent Context Block
5. 5Optional Domain Glossary

What it can do on your machine

Read from SKILL.md and the folder at commit 4594fb7. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • git

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Project Context Setup loads about 1.2k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 128 tokens; SKILL.md has 437 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~128

When it runs · the whole SKILL.md, loaded when a task matches

~1.2k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Mathews-Tom/armory at commit 4594fb7, republished under its MIT licence (© Mathews-Tom). 437 words, ~1,220 tokens.

name

project-context-setup

description

Scaffolds per-repository agent context so coding agents share the same issue tracker rules, triage label vocabulary, domain glossary, ADR layout, and handoff conventions. Triggers on: "set up project context", "configure agent docs", "create CONTEXT.md", "setup agent workflow", "agent issue tracker setup", "triage labels", "domain glossary for agents". Use when a repo needs durable context files before planning, triage, debugging, TDD, architecture review, or multi-agent implementation.

metadata.version

1.0.0

metadata.category

development

metadata.tags

agent-context, project-setup, domain-glossary, triage

metadata.difficulty

intermediate

metadata.phase

define

docs/agents/
├── issue-tracker.md
├── triage-labels.md
└── domain.md

## Agent context

### Issue tracker

See `docs/agents/issue-tracker.md` for where issues live and which operations agents may perform.

### Triage labels

See `docs/agents/triage-labels.md` for canonical triage roles and their concrete label strings.

### Domain docs

See `docs/agents/domain.md` for `CONTEXT.md`, `CONTEXT-MAP.md`, and ADR lookup rules.

© Mathews-Tom, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/project-context-setup of Mathews-Tom/armory.

• SKILL.md
• evals/cases.yaml
• references/agent-brief.md
• references/context-format.md
• references/out-of-scope.md

Open the folder on GitHubat commit 4594fb7