AGENTS.md@infrastructure/publishing/metadataA
AGENTS.md@infrastructure/publishing/metadata from docxology/template is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add docxology/template/infrastructure/publishing/metadata/AGENTS.md@git:20261006.d465449Pins git:20261006.d465449 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- docxology/template
- Path
infrastructure/publishing/metadata/AGENTS.md- Versions recorded
- 2
- Latest version
- git:20261006.d465449, committed Oct 6, 2026
- First version recorded
- Sep 8, 2026
- Size
- 1,792 bytes
- Repository stars
- 23
- License
- Apache-2.0
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# `infrastructure/publishing/metadata/` Metadata pipeline family, subpackaged out of the flat `infrastructure.publishing` namespace by RENDERING-LAYERING-1 phase 2b. **Not** the shared `infrastructure.metadata` leaf package: that one is a rendering-safe surface (repository-URL normalization, ebook metadata generation). This family is publishing-side pipeline code. ## Module graph | File | Role | | --- | --- | | `metadata_stage.py` | `run_metadata_package` — thin stage orchestrator (Stage 12): resolve project, load config, build ebook metadata, write `output/metadata/` | | `metadata_export.py` | `build_citation_cff`, `build_codemeta(_json)`, `build_zenodo(_json)`, `write_metadata_files` — generate `CITATION.cff`, `codemeta.json`, `.zenodo.json` from `manuscript/config.yaml` | | `metadata_export_cli.py` | `main` — `metadata-export` CLI (`python -m infrastructure.publishing.metadata.metadata_export_cli metadata-export --project <name>`) | | `metadata_from_config.py` | `publication_metadata_from_config(_dict)`, `load_publication_release_context` — single-parse metadata + deposit context + prior DOI | …
Read the whole file at its exact version.
How to install
mdr add docxology/template/infrastructure/publishing/metadata/AGENTS.md@sha256:2760a98aab45cd8cThe line at the top of this page pins the label git:20261006.d465449, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_c3442ftxrw2rgglt)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 8, 2026 and Oct 6, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.d465449 latest | 2026-10-06 | d465449 | 1,792 B | A | view · diff |
| git:20260908.26754c4 | 2026-09-08 | 26754c4 | 1,870 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1792 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
docxology/template · 23 stars · license Apache-2.0 · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_c3442ftxrw2rgglt GET https://markdownregistry.com/api/v1/resolve?ref=docxology/template/infrastructure/publishing/metadata/AGENTS.md GET https://markdownregistry.com/api/v1/blob/2760a98aab45cd8c01337bfe16a6b394861c84bc40d2325781499c614e95aa88
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: how to write a good AGENTS.md · AGENTS.md vs CLAUDE.md · which agent file does what.