AGENTS.md@src/KyberWeave.CoreA
AGENTS.md@src/KyberWeave.Core from dpalfery/kyber-weave is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add dpalfery/kyber-weave/src/KyberWeave.Core/AGENTS.md@git:20260815.8ac8cb1Pins git:20260815.8ac8cb1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- dpalfery/kyber-weave
- Path
src/KyberWeave.Core/AGENTS.md- Versions recorded
- 2
- Latest version
- git:20260815.8ac8cb1, committed Aug 15, 2026
- First version recorded
- Aug 2, 2026
- Size
- 4,572 bytes
- Repository stars
- 23
- License
- MIT
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
# KyberWeave.Core The engine. Everything the CLI and the MCP server do is implemented here; those two are thin hosts over this assembly. Read [`/AGENTS.md`](../../AGENTS.md) first for repository-wide rules. ## Core does not construct its own collaborators This is the constraint most easily broken by accident. Core defines **ports** and takes them as constructor arguments or factories. **Composition roots** — `DocsCommandComposition` in the CLI, `Program.cs` in the MCP server — decide which implementation is used. `ICodeGraphResolver` is the worked example: Core consumes the interface, the CLI and MCP host construct `CodeGraphResolverAdapter`, and tests inject `FakeCodeGraphResolver` so the whole drift and join surface can be driven without `sqlite3` on the machine. `DocumentIndexHost` takes `Func<ICodeGraphResolver>` and `Func<DocumentSet>` for the same reason. If you find yourself newing up a loader or a resolver inside Core, the dependency belongs in the caller. ## Layout | Directory | Holds | |---|---| | `Docs/` | Parsing, search, validation, export, scaffolding — the DocGraph engine | | `Skills/`, `Agents/` | Governance per artifact class | …
Read the whole file at its exact version.
How to install
mdr add dpalfery/kyber-weave/src/KyberWeave.Core/AGENTS.md@sha256:2c25443b60ef5d10The line at the top of this page pins the label git:20260815.8ac8cb1, 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_ybhzd2pgvmdyr6n3)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 2, 2026 and Aug 15, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260815.8ac8cb1 latest | 2026-08-15 | 8ac8cb1 | 4,572 B | A | view · diff |
| git:20260802.307d1a9 | 2026-08-02 | 307d1a9 | 4,326 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (4572 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
dpalfery/kyber-weave · 23 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ybhzd2pgvmdyr6n3 GET https://markdownregistry.com/api/v1/resolve?ref=dpalfery/kyber-weave/src/KyberWeave.Core/AGENTS.md GET https://markdownregistry.com/api/v1/blob/2c25443b60ef5d109668be9c74a2a8e6f570db66f385b79eabc518f8ab02c016
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.