guardlink: Instructions file for Codex

AGENTS.md

guardlink AGENTS.md is an instructions file for Codex, OpenCode from Bugb-Technologies/guardlink. It costs 935 tokens per session, scanned A, a copy of guardlink copilot-instructions.md, MIT.

Instructions for GuardLink, a security model that records facts next to code about exposure, data flow, protections, and accepted risks. GuardLink can query this information and validate changes.

In plain words
What is it for?
Use it before editing files, changing shared components, responding to scanner findings, or validating a completed security-sensitive change.
Why use it?
It helps agents check security context and the affected parts of a system instead of inferring those details from source code alone.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code; mentions Codex.

This is Bugb-Technologies/guardlink's own configuration. It tells Codex and OpenCode how to work on guardlink itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything guardlink configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Bugb-Technologies/guardlink. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Bugb-Technologies/guardlink/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Bugb-Technologies/guardlink

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for guardlink AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/bugb-technologies/guardlink/agents-md/github.svg)](https://agentmods.dev/instructions/bugb-technologies/guardlink/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/bugb-technologies/guardlink/agents-md"><img src="https://agentmods.dev/badge/instructions/bugb-technologies/guardlink/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.

agentmods 80×15 button for guardlink AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/bugb-technologies/guardlink/agents-md"><img src="https://agentmods.dev/badge/instructions/bugb-technologies/guardlink/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 935 This file is loaded in full into every session.
When invoked 935 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.1 $0.00935 $0.00935
Opus 5.5 $0.00374 $0.00374
Sonnet 5.5 $0.00187 $0.00187
Haiku 4.5 $0.00093 $0.00093

Measured yesterday against content hash 33ff07cb98f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

guardlink 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 yesterday.

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.

Origin

This is a copy

100% identical to guardlink copilot-instructions.md — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 48 lines

How it starts

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

This project carries a GuardLink threat model: security facts recorded next to the code they describe — what each component is exposed to, what mitigates it, how data flows. Ask it instead of inferring security context from the source: guardlink_context(file) before you edit a file, guardlink_graph before you change a shared component, guardlink_lookup("cwe:CWE-89") for a scanner finding, guardlink_paths for routes no control covers. Without MCP, guardlink status . and guardlink parse . answer the same.

Where annotations go: inline mode — in the doc-block comment of the code they describe, in that file's comment syntax, never in .gal sidecars. Placement in full: .guardlink/README.md; syntax and rules: docs/GUARDLINK_REFERENCE.md.

What you owe it back, in the same change as the code:

  • Annotate security-relevant code you write or change — endpoints, authentication and authorization (ownership and tenant checks included), validation, queries, file I/O, external calls, crypto, process spawning, configuration parsing. Reuse the ids in .guardlink/definitions.ts; never redefine one.
  • Code that hands an LLM agent a tool: @agents on the registration, @effects on the code that acts, @gates on an approval step (@reaches for a principal that is no agent). Syntax: the reference above.
  • Never write @accepts or @entitles — both are a human's decision. A risk with no control is @exposes + @audit; an entitlement is proposed with guardlink entitle --propose, and a human's acceptance writes it.
  • @confirmed needs reproduction evidence in hand; reading the code is not reproduction.
  • Before you finish: guardlink validate ., then guardlink diff HEAD~1 — did this change add exposure?

Read the full file on GitHub · 48 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. yesterday Changed · -5 tokens per session 33ff07cb98f4
  2. 3d ago Changed · +4 tokens per session 9c7be54abe44
  3. 11d ago Changed · +4 lines · +53 tokens per session ee693ba55821
  4. 12d ago Changed · +15 lines · +233 tokens per session d6710fd884e3
  5. 13d ago Changed · -169 lines · -3,884 tokens per session c5c95b9728aa
  6. 15d ago Changed · +3 tokens per session 7e6005048d10
  7. 17d ago Changed · -4 tokens per session fa91e2775eb5
  8. 24d ago Changed · +5 lines · +350 tokens per session 6665c4e7959d
  9. 25d ago Changed · +23 tokens per session 35e5a1539bc8
  10. 26d ago First seen · 193 lines · 4,162 tokens per session scan A 23aee9d77eb8

Subscribe to this mod's changes

guardlink AGENTS.md is an instructions file published in the GitHub repository Bugb-Technologies/guardlink (19 stars, last pushed yesterday), licensed MIT. It adds 935 tokens to every session, about $0.0037 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to guardlink copilot-instructions.md, differing in 11 lines, and is treated as a copy.

Related

Other instructions, from other repositories

vibetags com-example-service-OrderService.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for orderservice, rules for method calculatetax, rules for method processpayment, rules for method validateorder and context & focus.

PIsberg/vibetags · 553 tokens

vibetags com-example-security-SecurityConfig.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for securityconfig, locked status, rules for method getencryptionalgorithm, rules for method getkeyrotationhours and rules for method getmaxloginattempts.

PIsberg/vibetags · 281 tokens

vibetags com-example-service-TransactionalPaymentService.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for transactionalpaymentservice and strict exception handling.

PIsberg/vibetags · 104 tokens

vibetags com-example-service-NewAnnotationsShowcase-DraftKafkaIntegrationSpike.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for draftkafkaintegrationspike and experimental prototype.

PIsberg/vibetags · 93 tokens

vibetags com-example-service-NewAnnotationsShowcase-SandboxTestHelper.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for sandboxtesthelper and sandbox restriction.

PIsberg/vibetags · 98 tokens

vibetags com-example-concurrent-SessionCache.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for sessioncache and thread-safety guarantee.

PIsberg/vibetags · 71 tokens