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 skills add open-horizon-labs/repo-native-alignment --skill adr-syncgit clone --depth 1 https://github.com/open-horizon-labs/repo-native-alignmentWrote 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/skills/open-horizon-labs/repo-native-alignment/adr-sync)<a href="https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/adr-sync"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/adr-sync/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/skills/open-horizon-labs/repo-native-alignment/adr-sync"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/adr-sync.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.00030 | $0.00984 |
| Opus 5.5 | $0.00012 | $0.00394 |
| Sonnet 5.5 | $0.00006 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
adr-sync 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR Sync
Translate ADR prose into executable validation declarations and verify that ADRs are actually wired to real checks.
Arguments
$ARGUMENTS may be a single ADR path or a directory. Default to docs/ADRs/ when omitted.
Examples:
/rna-mcp:adr-sync docs/ADRs/001-event-bus-extraction-pipeline.md/rna-mcp:adr-sync docs/ADRs
Goal
Make ADRs mechanically checkable without introducing a second source of truth.
The ADR markdown stays canonical. This skill:
- adds or updates thin frontmatter validation declarations
- points them directly at real repo executables
- runs the repo-native ADR compile/check path
- reports gaps where no real executable exists yet
Valid executable references
Prefer normal test-suite checks first:
- exact cargo test names as reported by
cargo test -- --list - exact built-in ADR audit names when the claim is a code-shape constraint
- exact smoke fixture paths only when you need a repo-native delivery scenario
Use exact script paths only as a fallback when a claim genuinely cannot be expressed as a normal test or built-in audit yet.
Do not invent opaque evidence IDs or a registry layer in the ADR source. Do not fabricate validations that do not exist.
Process
1. Inspect the ADR(s)
- Read the ADR markdown and current frontmatter
- Extract the concrete claims that should be checkable
- Look for existing validations already present in the repo:
- exact
cargo test -- --listnames - built-in ADR audits via
repo-native-alignment adr audit <name> - smoke fixtures under
.github/fixtures/only when a repo-native delivery check is required - scripts under
.github/scripts/orscripts/only if no honest test or audit exists yet
- exact
2. Add/update frontmatter only where mapping is honest
Expected shape:
---
id: 001-event-bus-extraction-pipeline
status: implemented
validate:
cargo_tests:
- exact::cargo::test_name
audits:
- exact_audit_name
smoke:
- .github/fixtures/smoke
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 · 121 lines · 30 tokens per session scan A c0bb288d7b89
adr-sync is a skill published in the GitHub repository open-horizon-labs/repo-native-alignment (6 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 984 once invoked, about $0.0001 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-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.