Borrowing it
Nothing to install: this file belongs to thangnguyenworkspace/company-research-pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/thangnguyenworkspace/company-research-pipeline/main/AGENTS.mdgit clone --depth 1 https://github.com/thangnguyenworkspace/company-research-pipelineWrote 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/thangnguyenworkspace/company-research-pipeline/agents-md)<a href="https://agentmods.dev/instructions/thangnguyenworkspace/company-research-pipeline/agents-md"><img src="https://agentmods.dev/badge/instructions/thangnguyenworkspace/company-research-pipeline/agents-md/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/instructions/thangnguyenworkspace/company-research-pipeline/agents-md"><img src="https://agentmods.dev/badge/instructions/thangnguyenworkspace/company-research-pipeline/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01022 | $0.01022 |
| Opus 5 | $0.00511 | $0.00511 |
| Sonnet 5 | $0.00204 | $0.00204 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
company-research-pipeline 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 11d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Entry point for an agent operating or ingesting this repository. This is the single canonical agent-instruction file; CLAUDE.md imports it, so the two cannot drift. Edit this file, never CLAUDE.md. The human entry point is README.md.
What this is
company-research-pipeline is a company-research method packaged for Claude Code: four method documents, five slash-command skills, and four output templates that take one company from a scoped question to seven cited, confidence-tagged dossiers plus a synthesis. It is a stable snapshot distilled from one real diligence engagement. There is nothing to build or test; the repository is prose and skills, and the only thing that runs is a research engagement inside Claude Code.
How to navigate
| Path | What it is | Read it when |
|---|---|---|
.claude/commands/research-company.md |
The orchestrator: scoping, recon, the seven-topic walk | Starting or tracing a full engagement |
.claude/commands/research-topic.md |
One dossier through the eight-step loop (load, gather, compile, verify, attack, supplement, write, distribute) | Running or changing a single dossier |
.claude/commands/{exa-crawl,social-crawl,repo-recon}.md |
The three retrieval motions: Exa crawling, Apify social pulls, GitHub reconnaissance | Working on one retrieval motion |
method/01-pipeline.md |
The macro arc and the eight-step micro pipeline; the method's spine | You need how the pipeline is sequenced |
method/02-epistemics.md |
The [F/I/A + NN%] tag system, two-axis source grading, honesty rules |
Assigning tags or grading evidence |
method/03-topics.md |
The seven dossier subjects, their ownership boundaries, build order | Deciding what a dossier owns |
method/04-tools.md |
Verified Exa and Apify parameters, cost traps, silent failures | Before any tool call |
templates/ |
The exact output shapes for dossiers, gather and verification reports, the coverage map | Producing an engagement artifact |
research/ |
Working folders, one per company | The only surface an engagement writes to |
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.
- 11d ago First seen · 49 lines · 1,022 tokens per session scan A b22bc846e510
company-research-pipeline AGENTS.md is an instructions file published in the GitHub repository thangnguyenworkspace/company-research-pipeline (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,022 tokens to every session, about $0.0051 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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.
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).