Borrowing it
Nothing to install: this file belongs to UseJunior/safe-docx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/UseJunior/safe-docx/main/AGENTS.mdgit clone --depth 1 https://github.com/UseJunior/safe-docxWrote 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/usejunior/safe-docx/agents-md)<a href="https://agentmods.dev/instructions/usejunior/safe-docx/agents-md"><img src="https://agentmods.dev/badge/instructions/usejunior/safe-docx/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/usejunior/safe-docx/agents-md"><img src="https://agentmods.dev/badge/instructions/usejunior/safe-docx/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01107 | $0.01107 |
| Opus 5.5 | $0.00443 | $0.00443 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (46 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,107 tokens to every session, about $0.0044 per session on Opus 5.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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).