Borrowing it
Nothing to install: this file belongs to Litun/bloomy-linkedin-outreach. 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/Litun/bloomy-linkedin-outreach/main/AGENTS.mdgit clone --depth 1 https://github.com/Litun/bloomy-linkedin-outreachWrote 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/litun/bloomy-linkedin-outreach/agents-md)<a href="https://agentmods.dev/instructions/litun/bloomy-linkedin-outreach/agents-md"><img src="https://agentmods.dev/badge/instructions/litun/bloomy-linkedin-outreach/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/litun/bloomy-linkedin-outreach/agents-md"><img src="https://agentmods.dev/badge/instructions/litun/bloomy-linkedin-outreach/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.00228 | $0.00228 |
| Opus 5 | $0.00114 | $0.00114 |
| Sonnet 5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
bloomy-linkedin-outreach 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 10d 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.
What it actually says
For the AI agent running this project
Two separate modes - keep them separate, don't mix guidance between them.
First-time setup (once only)
Triggers: "let's set up the LinkedIn outreach", "set me up for LinkedIn automation like this ", or anything pointing at this project for the first time.
Follow SETUP.md exactly, start to finish - it has both the human steps and what you specifically need to do at each one. Do this once.
Regular runs (every scheduled run, forever after)
Trigger: the prompt says "Follow outreach_run.md." or "Follow weekly_review_run.md."
Just follow that file. Do not read SETUP.md, do not re-ask about registering with Bloomy or connecting the MCP, do not re-interview the user about the product, ICP, or templates - all of that is already done. The one exception: if CAMPAIGN.md, PRODUCT.md, ICP.md, or TEMPLATES.md still show a NOT CONFIGURED marker, stop and point the user at SETUP.md instead of guessing or improvising.
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.
- 10d ago First seen · 16 lines · 228 tokens per session scan A a4718f830fa9
bloomy-linkedin-outreach AGENTS.md is an instructions file published in the GitHub repository Litun/bloomy-linkedin-outreach (109 stars, last pushed 1mo ago), licensed MIT. It adds 228 tokens to every session, about $0.0011 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
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).
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.