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/htunesys/hexafn/copilot-instructionsgit clone --depth 1 https://github.com/hTuneSys/hexaFnWrote 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/htunesys/hexafn/copilot-instructions)<a href="https://agentmods.dev/instructions/htunesys/hexafn/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/htunesys/hexafn/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.1 | $0.02380 | $0.02380 |
| Opus 5 | $0.01190 | $0.01190 |
| Sonnet 5 | $0.00476 | $0.00476 |
| Haiku 4.5 | $0.00238 | $0.00238 |
Grade A, and why
hexaFn 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 today.
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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for hexaFn
⚡ PROJECT OVERVIEW
hexaFn is a modular, event-driven function pipeline framework powered by the 6F Lifecycle Flow: Feed → Filter → Format → Function → Forward → Feedback. This project follows Hexagonal Architecture (Ports & Adapters) with Domain-Driven Design (DDD) principles.
Company: hexaTune LLC
Maintainer: Husamettin ARABACI (@husamettinarabaci)
License: MIT (SPDX-compliant, REUSE Spec 3.3 compatible)
Repository: https://github.com/hTuneSys/hexaFn
🚨 CRITICAL ARCHITECTURE REQUIREMENTS
Hexagonal Architecture Structure (for all modules EXCEPT hexafn-core and hexafn-macros)
crates/<domain>/src/
├── domain/ # Core business rules (entities, value objects, domain services)
│ ├── entities/ # Aggregates and core business objects with identity
│ ├── value_objects/ # Immutable value types without identity
│ ├── events/ # Domain events for cross-domain communication
│ ├── services/ # Domain services containing business logic
│ └── contracts/ # Domain contracts and interfaces
├── application/ # Use cases, application services, port definitions
│ ├── commands/ # State-changing operations (CQRS Commands)
│ ├── queries/ # Read operations (CQRS Queries)
│ ├── ports/ # Interface definitions (dependency inversion)
│ └── services/ # Application orchestration services
├── infrastructure/ # Concrete implementations of output ports
│ ├── persistence/ # Database adapters, repositories
│ ├── messaging/ # Event publishing, message queue adapters
│ └── external/ # External API clients, third-party integrations
└── lib.rs # Crate entry point (re-exports and public API)
6F Lifecycle Flow Integration
- Feed: Ingest from external sources (events, APIs, queues)
- Filter: Pre-condition checks and gating
- Format: Normalize, transform, validate
- Function: Execute logic with user-defined behavior
- Forward: Route results to KV stores, topics, services
- Feedback: Log, trace, trigger, or audit
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.
- today First seen · 263 lines · 2,380 tokens per session scan A 76d4906ab822
hexaFn copilot-instructions.md is an instructions file published in the GitHub repository hTuneSys/hexaFn (11 stars, last pushed 10mo ago), licensed MIT. It adds 2,380 tokens to every session, about $0.0119 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-09-04.
Other instructions, from other repositories
traverse CLAUDE.md
Claude Code instructions for traverse-framework/traverse, covering traverse development guidelines, governance, active technologies, project structure and commands.
turso AGENTS.md
AGENTS.md instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
cli AGENTS.md
AGENTS.md instructions for googleworkspace/cli, covering agents.md, project overview, build & test, changesets and architecture.
azure-sdk-for-rust resourcemanager.instructions.md
Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
ton-rs AGENTS.md
AGENTS.md instructions for ston-fi/ton-rs, covering ton-rs agent guide, repository, boundaries, public api and ton invariants.