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/usejunior/safe-docx/agents-mdgit clone --depth 1 https://github.com/UseJunior/safe-docxWhat 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.01107 | $0.01107 |
| Opus 5 | $0.00553 | $0.00553 |
| Sonnet 5 | $0.00221 | $0.00221 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
safe-docx 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 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Instructions
These instructions are for AI assistants working in this project.
Always open @/openspec/AGENTS.md when the request:
- Mentions planning or proposals (words like proposal, spec, change, plan)
- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
- Sounds ambiguous and you need the authoritative spec before coding
Use @/openspec/AGENTS.md to learn:
- How to create and apply change proposals
- Spec format and conventions
- Project structure and guidelines
Keep this managed block so 'openspec update' can refresh the instructions.
ECMA-376 conformance
safe-docx targets a defined subset of ECMA-376 5th edition.
Spec conformance is a foundational property of this repo, not a side concern, so the
machinery lives at the repo root rather than under openspec/.
- Targeted sections + Non-Goals:
spec-compliance/registry/ecma-376.md - Vendored normative schemas:
spec-compliance/ecma-376/schemas/ - Citation-hygiene rules +
@conformancetag grammar:spec-compliance/AGENTS.md
When editing OOXML behavior, lead conformance claims with a @conformance ECMA-376 edition <N>, Part <N> § <SECTION>
JSDoc tag and demote internal #NNN issue references to @see. Tests use
testAllure.conformance({ spec, edition, part, section }). The lint
npm run check:conformance-citations enforces both.
Workflow Conventions
Follow all conventions in CONTRIBUTING.md. The rules below are mandatory for AI agents:
Branch Naming
- ALWAYS create a branch before committing. Never commit directly to
main. - Issue work:
{issue}-{short-description}-{YYYYMMDD}(e.g.,42-add-redline-support-20260221) - Minor fixes:
tweak-{description}(e.g.,tweak-fix-typo-in-readme)
Commits
- Use conventional commit format:
type(scope): imperative description - Valid types: feat, fix, refactor, test, docs, chore, ci, perf, style
- Scope to the package:
feat(docx-primitives):,fix(safe-docx):,refactor(docx-comparison): - Body MUST explain WHY, not just what. Longer is better.
- Reference the issue:
Fixes: #NorRef: #N
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 · 76 lines · 1,107 tokens per session scan A 53306551ab74
safe-docx AGENTS.md is an instructions file published in the GitHub repository UseJunior/safe-docx (40 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,107 tokens to every session, about $0.0055 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
daisyui code_generation_with_git.instructions.md
Instructions for saadeghi/daisyui, covering activation, initial setup, development loop, error handling and session end.
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
notfair-plugin AGENTS.md
AGENTS.md instructions for nowork-studio/notfair-plugin, covering notfair — skill resolver for ai agents, how to use this file, seo, paid ads and analytics.
mq commit.instructions.md
Instructions for harehare/mq: Use the following format for commit messages.
domscribe CLAUDE.md
Instructions for patchorbit/domscribe, covering claude.md, what is domscribe?, how to work on this codebase, commands and install dependencies (pnpm, not npm).
Commit Message
Comprehensive Conventional Commits guidelines for openwebui-extensions.