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/ssdeanx/agentstack/github-actions-ci-cd-best-practicesgit clone --depth 1 https://github.com/ssdeanx/AgentStackWhat 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.10873 | $0.10873 |
| Opus 5 | $0.05437 | $0.05437 |
| Sonnet 5 | $0.02175 | $0.02175 |
| Haiku 4.5 | $0.01087 | $0.01087 |
Grade E, and why
AgentStack github-actions-ci-cd-best-practices.instructions.md scanned grade E with 2 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- End of GitHub Actions CI/CD Best Practices Instructions --> Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Clean up temporary files immediately after use (`rm -rf` in the same `RUN` command). 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.
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.
- 2d ago First seen · 643 lines · 10,873 tokens per session scan E d0f1ee9dce01
AgentStack github-actions-ci-cd-best-practices.instructions.md is an instructions file published in the GitHub repository ssdeanx/AgentStack (44 stars, last pushed 4mo ago), with no licence file. It adds 10,873 tokens to every session, about $0.0544 per session on Opus 5. A static security scan graded it E with 2 findings (hidden instructions, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
embabel-agent CLAUDE.md
Claude Code instructions for embabel/embabel-agent, covering claude.md, important, coding style, working approach and advice for documentation in embabel-agent-docs.
a2a-python AGENTS.md
Instructions for a2aproject/a2a-python, covering agents.md, technology stack & architecture, mandatory workflow and optional extras.
hindsight CLAUDE.md
Instructions for vectorize-io/hindsight, covering claude.md, project overview, development commands, local development (api + ui) and start both api server and control plane ui.
codedb AGENTS.md
AGENTS.md instructions for justrach/codedb, covering codedb agent guidelines, what codedb is (and isn't), review guidelines, pre-merge verification and security-sensitive areas.
relay AGENTS.md
Instructions for AgentWorkforce/relay, covering git workflow rules, never push directly to main, correct workflow, ... do work .. and stop here - let user merge.
claude-code-settings copilot-instructions.md
Instructions for feiskyer/claude-code-settings, covering claude.md, environment setup, required dependencies, configuration and skills.