gitmesh string.instructions.md

Project instructions for GitMesh, a system that coordinates open-source AI agents using written policies.

In plain words
What is it for?
They belong to the GitMesh project; the concrete work they support is not specified.
Why use it?
They can give an agent project-specific guidance, but the excerpt only identifies a rule string.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/lf-decentralized-trust-labs/gitmesh/string
Clone the repo
git clone --depth 1 https://github.com/LF-Decentralized-Trust-labs/gitmesh

Made for: GitHub Copilot.

Per session 12 This file is loaded in full into every session.
When invoked 12 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00012 $0.00012
Opus 5 $0.00006 $0.00006
Sonnet 5 $0.00002 $0.00002
Haiku 4.5 $0.00001 $0.00001

Measured 2d ago against content hash 7fff8fad49b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gitmesh string.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 2d 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.

lib/workspace-adapters/fixtures/copilot/instructions-frontmatter/input-repo/.github/instructions/string.instructions.md · 5 lines

What it actually says

Rule string

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. 2d ago First seen · 5 lines · 12 tokens per session scan A 7fff8fad49b2

Subscribe to this mod's changes

gitmesh string.instructions.md is an instructions file published in the GitHub repository LF-Decentralized-Trust-labs/gitmesh (145 stars, last pushed 3d ago), licensed Apache-2.0. It adds 12 tokens to every session, about $0.0001 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.