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.
npx skills add Mathews-Tom/armory --skill project-context-setupgit clone --depth 1 https://github.com/Mathews-Tom/armoryWrote 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.
[](https://agentmods.dev/skills/mathews-tom/armory/project-context-setup)<a href="https://agentmods.dev/skills/mathews-tom/armory/project-context-setup"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/project-context-setup.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00109 | $0.01143 |
| Opus 5 | $0.00055 | $0.00571 |
| Sonnet 5 | $0.00022 | $0.00229 |
| Haiku 4.5 | $0.00011 | $0.00114 |
Grade A, and why
project-context-setup 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context Setup
Scaffold the repo-local context files that make agent workflows consistent across sessions: issue tracker rules, triage labels, domain glossary layout, ADR layout, agent brief format, and out-of-scope memory.
When To Use
| Use this skill | Use another package |
|---|---|
A repo lacks docs/agents/ context files |
adr-writer for one architecture decision |
| Agents need consistent domain vocabulary | task-decomposer for an already-scoped feature |
| Triage or issue publishing needs label conventions | github for direct GitHub CLI operations |
| Multi-agent work needs durable issue briefs | handoff for session-local continuation notes |
Reference Files
| File | Contents | Load When |
|---|---|---|
references/context-format.md |
CONTEXT.md and CONTEXT-MAP.md glossary format |
Creating or editing domain docs |
references/agent-brief.md |
Durable ready-for-agent issue brief contract |
Preparing issue handoff |
references/out-of-scope.md |
Persistent memory for rejected enhancements | Triage includes wontfix decisions |
Core Workflow
1. Explore
Inspect the actual repo state before writing:
git remote -vand.git/configfor issue tracker hints- root
AGENTS.mdandCLAUDE.md - root
CONTEXT.mdandCONTEXT-MAP.md docs/adr/and context-scoped ADR directories- existing
docs/agents/ - existing
.out-of-scope/
Report what exists and what is missing. Do not overwrite existing files blindly.
2. Choose Setup Values
Resolve these values with the user or from clear repo evidence:
| Decision | Default | Output |
|---|---|---|
| Issue tracker | GitHub if a GitHub remote exists, otherwise local markdown | docs/agents/issue-tracker.md |
| Triage labels | Canonical labels equal role names | docs/agents/triage-labels.md |
| Domain docs | Single root context | docs/agents/domain.md |
| Agent instructions file | Existing AGENTS.md, else existing CLAUDE.md |
Updated ## Agent context block |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 118 lines · 109 tokens per session scan A 172e06f2951e
project-context-setup is a skill published in the GitHub repository Mathews-Tom/armory (316 stars, last pushed 2d ago), licensed MIT. It adds 109 tokens to every session and 1,143 once invoked, about $0.0005 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.
Other skills, from other repositories
manager
A session-to-GitHub tracker that creates, updates, and reads issues across repositories, including their labels, parent epics, and project-board placement.
corp-doctor
A guided maintenance and setup tool for a Personal Corp system, meaning a business workflow built from AI agents, department repositories, and shared rules. It checks what exists before making changes.
pm-prioritize
Use when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano. Built-in decision tree picks the right framework based on data availability and decision context. Output is a transparent matrix, 2×2 Impact/Effort quadrant, and a Sprint allocation proposal. User-invoked only — do…
gh-issues
Use when creating, searching, updating, or managing GitHub issues via CLI. Triggers: "issue", "create issue", "gh issue", "task tracking", "context", "handoff", "resume task", "session context", "save progress", "active tasks", "in-progress", "my tasks", "open issues". Covers: gh commands, bulk operations, JSON/jq…
pm-roadmap
A roadmap update process that summarizes an iteration, a planned period of work, and its milestones, dependencies, and priorities.
pm-user-stories
A planning aid that breaks a large product requirement, or Epic, into smaller User Stories: short descriptions of work from a user’s point of view. It adds Given-When-Then acceptance checks, estimates, and a map for planning Sprints, which are fixed periods of development work.