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 agentmods add skills/darrenhinde/openagentscontrol/context-setupnpx skills add darrenhinde/OpenAgentsControl --skill context-setupgit clone --depth 1 https://github.com/darrenhinde/OpenAgentsControlWhat 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 | $0.00040 | $0.01136 |
| Opus 5 | $0.00020 | $0.00568 |
| Sonnet 5 | $0.00008 | $0.00227 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade C, and why
context-setup scanned grade C with 2 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Linux: sudo apt install git Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
&& echo "Project: ✓ installed — $(grep -o '"profile": "[^"]*"' .claude/.context-manifest.json | head -1 | cut -d'"' -f4) profile" \ How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install Context
Announce: "Let me set up your context files."
Why Context Files Matter
Context files are project-specific standards that every AI agent loads before writing code. Without them:
- Code won't follow your team's naming conventions or architecture patterns
- Security and quality standards won't be applied automatically
- Every agent starts from scratch instead of building on established patterns
With context files, every agent — coder, reviewer, tester — follows the same standards without you repeating yourself.
Quick Check
Run this single command to see everything relevant at once:
echo "=== Environment ===" && \
{ command -v git >/dev/null 2>&1 && echo "✓ git $(git --version | cut -d' ' -f3)" || echo "✗ git: not found — required"; } && \
{ command -v node >/dev/null 2>&1 && echo "✓ node $(node --version)" || echo " node: not found (bash installer works without it)"; } && \
echo "=== Context Status ===" && \
{ [ -f .claude/.context-manifest.json ] \
&& echo "Project: ✓ installed — $(grep -o '"profile": "[^"]*"' .claude/.context-manifest.json | head -1 | cut -d'"' -f4) profile" \
|| echo "Project: not installed"; } && \
{ [ -f ~/.claude/.context-manifest.json ] \
&& echo "Global: ✓ installed — $(grep -o '"profile": "[^"]*"' ~/.claude/.context-manifest.json | head -1 | cut -d'"' -f4) profile" \
|| echo "Global: not installed"; } && \
{ [ -f .oac.json ] && echo ".oac.json: ✓ exists" || echo ".oac.json: not found"; }
If already installed: show the status, ask if they want to reinstall (--force) or switch profiles.
If git is missing: stop and show the install instructions for git. Nothing else will work.
Ask Two Questions (then install)
Present both together as one message:
Where do you want to install context?
1. This project only — .claude/context/ (just for this repo)
2. Globally — ~/.claude/context/ (shared by all your projects)
Which profile?
standard — Core coding standards, security patterns, dev workflows (recommended, ~30s)
extended — Everything above + UI, data, content, product domains (~1 min)
all — The full library (~2 min)
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.
- 2d ago First seen · 129 lines · 40 tokens per session scan C 05b44153c327
context-setup is a skill published in the GitHub repository darrenhinde/OpenAgentsControl (4,815 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 1,136 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (asks for root, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
azure-openai-to-responses
Migrate Python apps from Azure OpenAI Chat Completions to the Responses API. Covers AzureOpenAI/AsyncAzureOpenAI client migration to the v1 endpoint, streaming, tools, structured output, multi-turn, EntraID auth, and model compatibility checks. Python-focused, Azure OpenAI-specific. USE FOR: migrate to responses API…
knowledge-base
Create and maintain a Markdown knowledge base that any AI agent can read, search, and update. Use when the user wants to start a knowledge base, add or update notes, organize docs/notes for an agent or LLM to consume, build an index of notes, or run a cleanup/maintenance pass on an existing MD knowledge base. Triggers…
peer-review
Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating…
statistical-power
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.