Borrowing it
Nothing to install: this file belongs to Northern-Lighthouse/swarm-mcp-server. 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/Northern-Lighthouse/swarm-mcp-server/main/AGENTS.mdgit clone --depth 1 https://github.com/Northern-Lighthouse/swarm-mcp-serverWrote 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/northern-lighthouse/swarm-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/northern-lighthouse/swarm-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/northern-lighthouse/swarm-mcp-server/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/northern-lighthouse/swarm-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/northern-lighthouse/swarm-mcp-server/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.00608 | $0.00608 |
| Opus 5 | $0.00304 | $0.00304 |
| Sonnet 5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
swarm-mcp-server 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 8d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - behaving well on the swarm bus
This file is for AI agents connected to a swarm-mcp-server instance.
It defines the etiquette that keeps a multi-agent swarm coherent; the human-facing setup doc is README.md, and examples/agent-prompt.md has a fuller prompt you can adapt.
Lifecycle
- Register once at startup:
agent_registerwith a stableagent_id, a human-readabledisplay_name, and honestcapabilities. Re-registering with the same id after a restart is fine. - Heartbeat every 15-20 seconds with
agent_heartbeatwhile you are alive. Agents silent past the timeout (default 30 s) are treated as offline; do not build on the assumption that a stale agent will return. - Deregister (
agent_deregister) when your task ends cleanly.
Working the task queue
- Claim before you work.
task_get_available, thentask_claim- the claim is atomic, so a successful claim means the task is yours; a failed claim means someone else got it, move on without retrying the same task. - Update status honestly with
task_update_statusas you progress, and always terminate a claimed task (completed or failed with a reason) - an abandoned claim blocks everyone downstream. - Respect dependencies: a task listed as available has its dependencies met; do not start work on tasks you merely see in
task_list.
Messaging
message_sendfor one recipient,message_broadcastfor everyone; poll withmessage_pollon your own cadence (heartbeat time is a natural moment).- Mark what you have handled (
message_mark_read) so conversation state stays meaningful. - Keep messages operational: what you did, what you need, what changed. Put durable findings in the knowledge base instead.
Knowledge base
knowledge_storefindings other agents will need (decisions, gotchas, interface contracts), with searchable titles.- Search before you re-derive:
knowledge_search(keyword) orknowledge_semantic_search(vector, when the host runs embeddings).
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.
- 8d ago First seen · 43 lines · 608 tokens per session scan A 4c9aa0148c75
swarm-mcp-server AGENTS.md is an instructions file published in the GitHub repository Northern-Lighthouse/swarm-mcp-server (0 stars, last pushed 25d ago), licensed MIT. It adds 608 tokens to every session, about $0.0030 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).
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.
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.