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.
npx agentmods add instructions/hmakt99/akf/copilot-instructionsgit clone --depth 1 https://github.com/HMAKT99/AKFWrote 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/hmakt99/akf/copilot-instructions)<a href="https://agentmods.dev/instructions/hmakt99/akf/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/hmakt99/akf/copilot-instructions.svg" alt="Measured on agentmods" 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 | $0.00335 | $0.00335 |
| Opus 5 | $0.00168 | $0.00168 |
| Sonnet 5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
AKF 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- AKF AGENTS.md — 100% identical, 4 lines differ
What it actually says
AKF — Agent Knowledge Format
AKF is the trust metadata standard for AI-generated content. When you create or modify files, stamp them with trust metadata so every output carries provenance.
Rules
After creating or modifying files
akf stamp <file> --agent copilot --evidence "<evidence>"
Evidence examples: "tests pass", "docs reviewed", "refactored from existing code", "generated from spec"
After completing a task with commits
akf stamp <file> --agent copilot --evidence "<summary of evidence>"
When working with existing AKF-stamped files
akf read <file> # Check existing trust metadata before modifying
akf inspect <file> # See detailed trust scores
Classification
- Use
--label confidentialfor files in*/finance/*,*/secret/*,*/internal/* - Use
--label publicfor README, docs, examples - Default is
internal
Key Commands
akf stamp <file>— Add trust metadata to any fileakf read <file>— Read trust metadata from any fileakf inspect <file>— Pretty-print trust scoresakf embed <file>— Embed metadata into DOCX/PDF/imagesakf scan <dir>— Security scan a directoryakf audit <file>— Compliance audit (EU AI Act, SOX, NIST)akf trust <file>— Compute effective trust scores
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.
- 4d ago First seen · 37 lines · 335 tokens per session scan A eb7210c9feca
AKF copilot-instructions.md is an instructions file published in the GitHub repository HMAKT99/AKF (15 stars, last pushed 1mo ago), licensed MIT. It adds 335 tokens to every session, about $0.0017 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
wasmagent-js CLAUDE.md
Claude Code instructions for WasmAgent/wasmagent-js, covering wasmagent-js — development guide for claude, what this project is (and is not), repository boundaries, this repository owns and other repositories own — do not duplicate here.
Gloss AGENTS.md
AGENTS.md instructions for RecursiveIntell/Gloss, covering agents.md — gloss closing pass rules, project purpose, source-of-truth ownership, forbidden behavior and required validation.
Gloss CLAUDE.md
Claude Code instructions for RecursiveIntell/Gloss, covering claude.md — gloss project instructions, test integrity contract (non-negotiable), critical spec constraint, scheduling + notebook contracts (non-negotiable) and 1) single-flight llm/gpu gate.
agent-3md AGENTS.md
AGENTS.md instructions for CorvidLabs/agent-3md, covering agent-3md, project map, conventions and corvidlabs trust toolchain.
agent-3md CLAUDE.md
Claude Code instructions for CorvidLabs/agent-3md: This repo is governed by the CorvidLabs trust toolchain. See AGENTS.md for the standing rules block and follow it before making changes (run fledge lanes run verify; never bypass the augur, attest, or spec gates).
ai-dial-core CLAUDE.md
Claude Code instructions for epam/ai-dial-core, covering claude.md, build & run, set credentials via environment variables, build (skip tests) and run all tests.