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/glowbom/glowbom-oss/agents-mdgit clone --depth 1 https://github.com/glowbom/glowbom-ossWrote 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/glowbom/glowbom-oss/agents-md)<a href="https://agentmods.dev/instructions/glowbom/glowbom-oss/agents-md"><img src="https://agentmods.dev/badge/instructions/glowbom/glowbom-oss/agents-md.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.00151 | $0.00151 |
| Opus 5 | $0.00076 | $0.00076 |
| Sonnet 5 | $0.00030 | $0.00030 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
glowbom-oss AGENTS.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 5d 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.
What it actually says
Workspace Instructions
Public Repository Boundary
The complete oss folder is copied into the separate public Glowbom OSS repository.
- Keep this folder self-contained and independently buildable.
- Do not depend on files from the parent repository.
- Do not include private plans, production configuration, customer data, or internal-only assets.
- Keep public setup instructions, licenses, security guidance, and contributor information inside this folder.
- Use relative paths that continue to work when oss becomes the public repository root.
- Before a public sync, check tracked and untracked files for credentials, local logs, generated media, and build output.
Commit Messages
- After making code changes, always suggest a one-line conventional commit message.
- Prefer the format
type: summary.
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.
- 5d ago First seen · 17 lines · 151 tokens per session scan A 463902c4d079
glowbom-oss AGENTS.md is an instructions file published in the GitHub repository glowbom/glowbom-oss (162 stars, last pushed 7d ago), licensed MIT. It adds 151 tokens to every session, about $0.0008 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.
Other instructions, from other repositories
pickleshell AGENTS.md
AGENTS.md instructions for pickleshell/pickleshell, covering agents.md, scope, operational installation route, identifier terminology and required checks.
openai-cookbook AGENTS.md
AGENTS.md instructions for openai/openai-cookbook, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
azure-search-openai-demo AGENTS.md
AGENTS.md instructions for Azure-Samples/azure-search-openai-demo, covering instructions for coding agents, overall code layout, adding new data, adding a new azd environment variable and adding a new setting to "developer settings" in rag app.
openagent CLAUDE.md
Claude Code instructions for the-open-agent/openagent, covering claude.md, commands, architecture, backend (go / beego) and frontend (react).
gptme AGENTS.md
AGENTS.md instructions for gptme/gptme, covering agent instructions for gptme, git workflow, code style, testing and project structure.
awesome-ChatGPT-repositories CLAUDE.md
Claude Code instructions for taishi-i/awesome-ChatGPT-repositories, covering awesome-chatgpt-repositories — claude code guide, repository structure, plugin skill (when installed via /plugin), local standalone command (when repo is cloned) and compact data format (plugins/awesome-chatgpt-search/data/).