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 instructions/usestrix/strix/agents-mdgit clone --depth 1 https://github.com/usestrix/strixWhat 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.01010 | $0.01010 |
| Opus 5 | $0.00505 | $0.00505 |
| Sonnet 5 | $0.00202 | $0.00202 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade C, and why
strix AGENTS.md 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 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -sSL https://strix.ai/install | bash # install Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sSL https://strix.ai/install | bash # install How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strix — Agent Guide
Strix is an open-source autonomous AI pentesting tool. This file is for AI coding agents that want to use Strix (run security scans) or contribute to it.
Using Strix from an agent
Install the agent skills for step-by-step workflows:
npx skills add usestrix/strix
penetration-testing-with-strix— run a headless pentest against code, URLs, domains, or IPs and read results (covers both run modes below)managed-pentesting-with-strix— drive the managed app.strix.ai platform via REST (no local Docker/LLM needed)fix-security-vulnerabilities-with-strix— remediate findings and re-run Strix to verifyci-security-scanning-with-strix— add PR scanning to CI/CD (self-hosted CLI or managed app)
Target-specific workflows built on the same engine:
application-security-testing— whole-product AppSec review: pick the right test per asset, then rank the resultsweb-app-penetration-testing— black-box pentest of a live web app or staging siteapi-security-testing— REST/GraphQL APIs and the OWASP API Security Top 10 (BOLA/IDOR, authz)owasp-top-10-testing— systematic OWASP Top 10 assessment with honest per-category coveragefind-security-vulnerabilities-in-code— white-box review of a repo or working tree
Two ways to run, same engine — pick per situation:
- Open-source CLI (self-hosted): free, fully local, BYO LLM key, needs Docker. Best for local dev loops, air-gapped/offline, and full control.
curl -sSL https://strix.ai/install | bash # install export STRIX_LLM="openai/gpt-5.4" # any LiteLLM model id export LLM_API_KEY="<key>" strix -n -t ./ --scan-mode quick --max-budget 10 # headless scan; always use -n- Requires Docker running. Scans take minutes (
quick) to hours (deep) — run in the background. - Exit codes (headless):
0clean,1fatal error,2vulnerabilities found. A0only covers what was analyzed — checkrun.json(status,llm_usage.costvs the budget) before calling a run clean. - Artifacts in
strix_runs/<run-name>/:penetration_test_report.md,vulnerabilities/*.md,vulnerabilities.json,findings.sarif(SARIF 2.1.0),run.json.
- Requires Docker running. Scans take minutes (
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.
- yesterday First seen · 58 lines · 1,010 tokens per session scan C ea19fffafb90
strix AGENTS.md is an instructions file published in the GitHub repository usestrix/strix (59,426 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,010 tokens to every session, about $0.0051 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
swarms CLAUDE.md
Instructions for kyegomez/swarms, covering claude.md — swarms framework guide, installation & setup, any provider supported by litellm works, project layout and core primitive: agent.
langgraphjs AGENTS.md
Instructions for langchain-ai/langgraphjs, covering repository instructions and corridor security analysis.
NanoResearch AGENTS.md
Instructions for OpenRaiser/NanoResearch, covering nanoresearch — codex integration mode, core goal, pipeline, workspace convention and paper modes.
NanoResearch CLAUDE.md
Instructions for OpenRaiser/NanoResearch, covering nanoresearch — claude code integration mode, core goal, pipeline, workspace convention and paper modes.
wanaku CLAUDE.md
Instructions for wanaku-ai/wanaku, covering wanaku, core guidelines, quick start, build info and architecture.
violin AGENTS.md
Instructions for Strategic-Automation/violin, covering strategic-automation/violin — ai developer guidance, 1. stack & setup, 2. mandatory verification commands, 3. code conventions & architecture and 4. git & branching strategy.