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/hiero-ledger/solo/copilot-instructionsgit clone --depth 1 https://github.com/hiero-ledger/soloWrote 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/hiero-ledger/solo/copilot-instructions)<a href="https://agentmods.dev/instructions/hiero-ledger/solo/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/hiero-ledger/solo/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.01491 | $0.01491 |
| Opus 5 | $0.00745 | $0.00745 |
| Sonnet 5 | $0.00298 | $0.00298 |
| Haiku 4.5 | $0.00149 | $0.00149 |
Grade A, and why
solo 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot instructions for hiero-ledger/solo
These instructions apply to all code suggestions in this repository. They mirror CLAUDE.md and the
full TypeScript style guide at docs/contributing/typescript-code-style.md — read that guide for the
authoritative rules and rationale. The conventions below are the ones violated most often.
Highest-frequency rules
-
No exported functions. Behavior (resolvers, orchestrators, computations) is grouped on a class as
staticmethods. Do not writeexport function foo(...)orexport const foo = () => …at module scope. Pure data — constants, types, simple factories — may still be exported. A helper used by only one class becomes aprivate staticmember of that class. (§3.4.5, §10.3.1–§10.3.2; enforced by thesolo/no-exported-functionESLint rule — an error insrc/integration/**.)// ❌ Avoid export function detectFatalContainerError(pod: V1Pod): string | undefined { ... } // ✅ Prefer export class K8ClientPods { public static detectFatalContainerError(pod: V1Pod): string | undefined { ... } } -
One exported class/interface per file, with the file named in kebab-case matching the class/interface name (e.g.
class KubeValidation→kube-validation.ts,interface FooBarOptions→foo-bar-options.ts). (§3.5; enforced bysolo/exported-interface-in-own-filelint rule for interfaces — a warning today, escalating to error once legacy barrel files are split) Splitting types into separate files can create circular dependencies — verify withnpx dpdm --no-warning --no-tree --exit-code circular:1 ./solo.tsafter any such move. Break cycles by extracting a minimal shared interface rather than having two files import each other. -
import type— use the inline formimport {type Foo} from '...', neverimport type {Foo}. -
Explicit types on every variable declaration and every callback (including
it()/describe()callbacks in tests). (§6.1) -
No banned abbreviations in identifiers or file names (
fn,vars,opts,err,cb, …). Use full words (function→ spell out the role,options,error,callback). (§5.1.2) -
SPDX header required on every source file. TypeScript:
// SPDX-License-Identifier: Apache-2.0as the very first line (enforced by ESLint). Shell scripts under.github/workflows/script/: add# SPDX-License-Identifier: Apache-2.0on the line immediately after#!/bin/bash— ESLint does not cover shell files, so apply it manually.
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.
- 3d ago First seen · 106 lines · 1,491 tokens per session scan A 3dd1ab1a71c0
solo copilot-instructions.md is an instructions file published in the GitHub repository hiero-ledger/solo (43 stars, last pushed today), licensed Apache-2.0. It adds 1,491 tokens to every session, about $0.0075 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-01.
Other instructions, from other repositories
patternfly-react-seed AGENTS.md
Instructions for patternfly/patternfly-react-seed, covering agent instructions (patternfly react seed), what this project is, stack, commands to run before you consider work done and repository layout.
tsed-cli AGENTS.md
AGENTS.md instructions for tsedio/tsed-cli, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
maui uitests.instructions.md
Instructions for dotnet/maui, covering ui testing guidelines for .net maui, ui test structure, two-project requirement, base class and infrastructure and naming conventions.
maui performance-hotpaths.instructions.md
Instructions for dotnet/maui, covering performance-critical path rules, hot paths in maui, allocation avoidance, caching and invalidation and collection iteration.
starknet-agentic CLAUDE.md
Instructions for keep-starknet-strange/starknet-agentic, covering starknet agentic -- development context, cairo, typescript, skills and git.
openmcp-client CLAUDE.md
Instructions for LSTM-Kirigaya/openmcp-client, covering claude.md, development commands, setup and installation, development and service development.