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.
curl -O https://raw.githubusercontent.com/Bugb-Technologies/guardlink/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/Bugb-Technologies/guardlinkWrote 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/bugb-technologies/guardlink/copilot-instructions)<a href="https://agentmods.dev/instructions/bugb-technologies/guardlink/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/bugb-technologies/guardlink/copilot-instructions/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/bugb-technologies/guardlink/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/bugb-technologies/guardlink/copilot-instructions.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.00811 | $0.00811 |
| Opus 5.5 | $0.00324 | $0.00324 |
| Sonnet 5.5 | $0.00162 | $0.00162 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
guardlink copilot-instructions.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.
Copies of this mod
2 near-identical copies found in the catalogue:
- guardlink AGENTS.md — 100% identical, 11 lines differ
- guardlink CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guardlink — Project Instructions
GuardLink — Security Model
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:
@agentson the registration,@effectson the code that acts,@gateson an approval step (@reachesfor a principal that is no agent). Syntax: the reference above. - Never write
@acceptsor@entitles— both are a human's decision. A risk with no control is@exposes+@audit; an entitlement is proposed withguardlink entitle --propose, and a human's acceptance writes it. @confirmedneeds reproduction evidence in hand; reading the code is not reproduction.- Before you finish:
guardlink validate ., thenguardlink diff HEAD~1— did this change add exposure?
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.
- yesterday Changed · -5 tokens per session 746e9a188343
- 3d ago Changed · +4 tokens per session 7c03ba4af465
- 11d ago Changed · -3 tokens per session 44f1e4f3386e
- 12d ago Changed · +8 lines · +165 tokens per session 24c53fd03ce8
- 13d ago Changed · -169 lines · -3,884 tokens per session c5c95b9728aa
- 15d ago Changed · +3 tokens per session 7e6005048d10
- 17d ago Changed · -4 tokens per session fa91e2775eb5
- 24d ago Changed · +5 lines · +350 tokens per session 6665c4e7959d
- 25d ago Changed · +23 tokens per session 35e5a1539bc8
- 26d ago First seen · 193 lines · 4,162 tokens per session scan A 23aee9d77eb8
guardlink copilot-instructions.md is an instructions file published in the GitHub repository Bugb-Technologies/guardlink (19 stars, last pushed yesterday), licensed MIT. It adds 811 tokens to every session, about $0.0032 per session on Opus 5.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
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.
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.
vibetags com-example-service-TransactionalPaymentService.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for transactionalpaymentservice and strict exception handling.
vibetags com-example-service-NewAnnotationsShowcase-DraftKafkaIntegrationSpike.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for draftkafkaintegrationspike and experimental prototype.
vibetags com-example-service-NewAnnotationsShowcase-SandboxTestHelper.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for sandboxtesthelper and sandbox restriction.
vibetags com-example-concurrent-SessionCache.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for sessioncache and thread-safety guarantee.