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/specterops/configmanbearpig/agents-mdgit clone --depth 1 https://github.com/SpecterOps/ConfigManBearPigWrote 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/instructions/specterops/configmanbearpig/agents-md)<a href="https://agentmods.dev/instructions/specterops/configmanbearpig/agents-md"><img src="https://agentmods.dev/badge/instructions/specterops/configmanbearpig/agents-md.svg" alt="Measured on agentmods" height="20"></a>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 | $0.02488 | $0.02488 |
| Opus 5 | $0.01244 | $0.01244 |
| Sonnet 5 | $0.00498 | $0.00498 |
| Haiku 4.5 | $0.00249 | $0.00249 |
Grade A, and why
ConfigManBearPig AGENTS.md 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 5d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Agent Guidance
This file should always be used as the entrypoint for agents working in this repository. Keep it generic and concise.
Project-specific standards live under .agents/standards/ and task-specific guidance lives in the relevant skill files
under .agents/skills/.
Before Editing
- Read
.agents/standards/openhound.mdbefore making OpenHound collector changes. - Read
.agents/standards/workflow.mdbefore developing a new collector or making broad collector changes. - Read
ARCHITECTURE.mdbefore touching any cross-cutting collector subsystem (the per-host phased pipeline, recursive discovery / target allow-list, the Windows authentication stacks underclients/, the logging/diagnostics layer, the Windows-specific fixes, or the preproc/convert design). It explains how and why this extension diverges from a stock OpenHound (REST-API-only) collector. Update the relevant section ofARCHITECTURE.mdin the same change whenever you alter one of those subsystems, and fix anyfile:linereferences your change invalidates. Add a new section if you introduce a new category of divergence. openhound-collector-commonis a separate published package — treat it exactly likeopenhoundcore. The Windows auth stacks, the per-target logging layer, the push→pull streaming bridge (StreamBridge), and the DNS resolver live there, shared with the MSSQL collector; this repo'sclients/*,log_context.py, andphased_pipeline/streams.pyare thin adapters/re-exports over it (seeARCHITECTURE.md→ "Where this code lives"). It is declared as a capped version range in[project.dependencies];[tool.uv.sources]optionally redirects it to a sibling checkout at../openhound-collector-commonfor local work, and that redirect never reaches the published wheel. Trace into the library to understand behaviour, but do not treat editing it as part of a change here — it affects both collectors and it releases on its own tag. If a task seems to need a shared-library change, stop and say so.- Load the
openhoundskill from.agents/skills/openhound/for task-specific workflows.
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.
- 5d ago First seen · 211 lines · 2,488 tokens per session scan A b7575d2a2417
ConfigManBearPig AGENTS.md is an instructions file published in the GitHub repository SpecterOps/ConfigManBearPig (145 stars, last pushed 26d ago), licensed Apache-2.0. It adds 2,488 tokens to every session, about $0.0124 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.