termstack terminal-rules.instructions.md

Project instructions for working on termstack, including its terminal environment, operating rules, and preferred practices.

In plain words
What is it for?
Use them when navigating the terminal, checking the environment, deciding how to run commands, or following termstack’s stated rules.
Why use it?
They help an agent understand the project’s expectations and verify commands before running them.

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/zebbern/termstack/terminal-rules
Clone the repo
git clone --depth 1 https://github.com/zebbern/termstack

Made for: GitHub Copilot.

Per session 1,246 This file is loaded in full into every session.
When invoked 1,246 The same file — it is already loaded in full.
Security scan C 1 finding. Scan, not verified.
Origin unknown 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.01246 $0.01246
Opus 5 $0.00623 $0.00623
Sonnet 5 $0.00249 $0.00249
Haiku 4.5 $0.00125 $0.00125

Measured yesterday against content hash 28f3214d63a9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

termstack terminal-rules.instructions.md scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- `rm -rf`
.github/instructions/terminal-rules.instructions.md · 124 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. yesterday First seen · 124 lines · 1,246 tokens per session scan C 28f3214d63a9

Subscribe to this mod's changes

termstack terminal-rules.instructions.md is an instructions file published in the GitHub repository zebbern/termstack (5 stars, last pushed 4mo ago), with no licence file. It adds 1,246 tokens to every session, about $0.0062 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.