ghostlink AGENTS.md

A set of AGENTS.md instructions for coordinating software work between a lead agent and specialized helper agents. It defines roles, file boundaries, handoffs, and required checks.

In plain words
What is it for?
Planning repository work, assigning scoped tasks, reviewing changes, and running tests, linting, type checks, and builds.
Why use it?
It gives a development team a shared operating model so agents do not overwrite unrelated files or skip verification.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/bgorzelic/ghostlink/agents-md
Clone the repo
git clone --depth 1 https://github.com/bgorzelic/ghostlink

Made for: Codex, OpenCode.

Per session 461 This file is loaded in full into every session.
When invoked 461 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00461 $0.00461
Opus 5 $0.00230 $0.00230
Sonnet 5 $0.00092 $0.00092
Haiku 4.5 $0.00046 $0.00046

Measured 2d ago against content hash 0aed6ff3b146, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ghostlink 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 2d 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.

AGENTS.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Operating Model

GhostLink development runs as a structured agentic swarm with a single Orchestrator and scoped sub-agents.

  • Orchestrator: Primary Claude Code instance. Owns plan, milestones, and final verification.
  • Sub-agents: Spawned only when isolation or parallelism improves output. Each has a declared scope and must not modify files outside it.

Global Rules

Every agent (orchestrator or sub-agent) must:

  1. Operate only within the repo root
  2. Return structured outputs (diffs + command outputs + assumptions)
  3. Run verification after edits (npm test && npm run lint && npm run typecheck && npm run build)
  4. Avoid broad refactors unless explicitly requested
  5. Never introduce arbitrary command execution surfaces

Roles

Role Scope Responsibility
Orchestrator Entire repo Plan, scope, milestones, merge, verify
Protocol Engineer src/server.ts, src/index.ts, src/types/* Server factory, tool registration, transport
Toolsmith src/core/tools/*, src/core/utils/*, src/core/policy/* Tool implementation, deterministic output
Security Reviewer docs/SECURITY.md, src/core/policy/* Threat model, audit, hardening recommendations
Test Engineer tests/* Unit + golden tests per tool
Docs Engineer docs/*, root markdown files Schema docs, architecture, prompts

Full sub-agent prompt templates: docs/PROMPTS.md

Handoff Contract

Every sub-agent response must include:

  1. Unified diff or exact file contents
  2. Commands executed and their output
  3. Assumptions and risks identified
  4. Next actions (if blocked or incomplete)

Long-Term Vision Alignment

All agents must preserve forward-compatibility with:

  • Remote transport (Phase 2)
  • Memory integration (Phase 3)
  • Runtime orchestration (Phase 3)

Never hard-code decisions that block Phase 2 or Phase 3 expansion. GhostLink remains the capability plane. Orchestration lives elsewhere.

Read the full file on GitHub · 52 lines

Changes

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.

  1. 2d ago First seen · 52 lines · 461 tokens per session scan A 0aed6ff3b146

Subscribe to this mod's changes

ghostlink AGENTS.md is an instructions file published in the GitHub repository bgorzelic/ghostlink (0 stars, last pushed 28d ago), licensed ISC. It adds 461 tokens to every session, about $0.0023 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.