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 UKGovernmentBEIS/inspect_evals --skill build-repo-contextgit clone --depth 1 https://github.com/UKGovernmentBEIS/inspect_evalsWrote 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/ukgovernmentbeis/inspect_evals/build-repo-context)<a href="https://agentmods.dev/skills/ukgovernmentbeis/inspect_evals/build-repo-context"><img src="https://agentmods.dev/badge/skills/ukgovernmentbeis/inspect_evals/build-repo-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.
<a href="https://agentmods.dev/skills/ukgovernmentbeis/inspect_evals/build-repo-context"><img src="https://agentmods.dev/badge/skills/ukgovernmentbeis/inspect_evals/build-repo-context.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.01989 |
| Opus 5 | $0.00028 | $0.00994 |
| Sonnet 5 | $0.00011 | $0.00398 |
| Haiku 4.5 | $0.00006 | $0.00199 |
Grade A, and why
build-repo-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 12d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Repo Context
Crawl GitHub history (PRs, issues, review comments) and distill institutional knowledge into agent_artefacts/repo_context/REPO_CONTEXT.md. This document helps worker agents understand repo conventions, common mistakes, and known tech debt before making changes.
Workflow
1. Setup
- Create
agent_artefacts/repo_context/if it doesn't exist - Read existing
agent_artefacts/repo_context/REPO_CONTEXT.mdif present (will be updated, not replaced)
2. Identify What's New
Use the header of REPO_CONTEXT.md to determine what to process. The header contains the last-updated date and PR range (e.g., PRs processed: #965-#1050).
- First run (no
REPO_CONTEXT.md): Fetch the most recent 50 merged PRs + all open issues - Incremental runs: Fetch PRs merged after the highest PR number in the header, and issues updated since the last-updated date
Use the gh CLI to list candidates:
# First run: recent merged PRs
gh pr list --state merged --limit 50 --json number,title,labels,additions,deletions,reviewDecision,mergedAt
# Incremental: PRs merged since last crawl
gh pr list --state merged --search "merged:>YYYY-MM-DD" --limit 50 --json number,title,labels,additions,deletions,reviewDecision,mergedAt
# Open issues
gh issue list --state open --limit 100 --json number,title,labels,createdAt,updatedAt
3. Triage
Fast pass over PR titles and metadata. Skip these categories (they rarely contain design insights):
- Dependency bumps (titles matching
bump,update dependencies,renovate,dependabot) - Changelog-only updates (titles matching
changelog,scriv) - Bot-generated PRs with no review comments
- PRs with fewer than 5 lines changed and no review comments
Prioritize PRs that have:
- Review comments (especially multiple rounds — that's where design discussion lives)
- Changes touching shared utilities (
src/inspect_evals/utils/,CONTRIBUTING.md,BEST_PRACTICES.md,AGENTS.md)
Cap at 50 PRs per run to keep execution time reasonable.
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.
- 12d ago First seen · 175 lines · 55 tokens per session scan A a7d45bcd0deb
build-repo-context is a skill published in the GitHub repository UKGovernmentBEIS/inspect_evals (665 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,989 once invoked, about $0.0003 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.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.