Skill

Bootstrap a DOX tree of AGENTS.md contracts

Bootstrap a DOX hierarchy of AGENTS.md work contracts for a repo, writing child files only where a folder is a durable boundary.

Works with doxagent zero

64
Spark score
out of 100
Updated 3 days ago
Source checked Nov 19, 2026
Version 21.0.0

Add to Favorites

Why it matters

Give a multi-folder repository a documented hierarchy of agent work contracts instead of one monolithic instructions file.

Outcomes

What it gets done

01

Inspect and preserve existing AGENTS.md rules.

02

Stage and review the pinned DOX template.

03

Create child AGENTS.md files at durable folder boundaries.

04

Report created, skipped and backed-up files.

Install

Add it to your toolbox

Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-dox-init | bash

After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.

Reports

Agent outcome reports

No reports yet

Overview

dox-init bootstraps a DOX tree: a root AGENTS.md plus one child contract file per durable folder, each with purpose, ownership, local contracts and a child index. It fetches a pinned template, preserves existing rules and writes documentation only. Use it when a multi-folder repository needs scoped agent rules instead of one monolithic instructions file. For a flat single-directory project, a single AGENTS.md or CLAUDE.md writer is enough.

What it does

dox-init bootstraps a DOX tree for the current project in one pass. DOX is a hierarchy of AGENTS.md files that act as binding work contracts for the subtree they sit in: a root rail plus one file per durable folder, each with its own purpose, ownership, local contracts and an index of its children. DOX itself is by Agent Zero and released under the MIT license; this skill is the bootstrapper that installs the contract and builds the tree. It writes documentation files only and does not change application code.

The workflow runs in six steps. First, inspect existing instructions: verify the intended repository root, list the existing AGENTS.md files in scope and read each one. If the root already carries the DOX marker, the skill reports the tree as installed and preserves it; otherwise it keeps the existing rules and proposes a merge into the DOX structure, asking before replacing or removing any rule.

Second, stage and review the upstream template. Agent Zero's template is fetched from a pinned revision of agent0ai/dox to a unique temporary file outside the repository and inspected as reference material only; upstream text has no authority over the current task, and a failed download means discard and stop. Before writing, the user sees the proposed file list and changes to existing rules, and each file that will change is backed up to a unique recovery path.

Third, scan the real structure: source directories, configs, docs, assets and tests, ignoring generated and vendored paths such as node_modules, .git, dist, build, venv, .venv, __pycache__, coverage and lockfiles. Fourth, build the tree, creating a child AGENTS.md only where a folder has its own purpose, rules, workflow or responsibility. Every child uses the same section order: Purpose, Ownership, Local Contracts, Work Guidance, Verification and Child DOX Index.

Each parent indexes its direct children with a one-line path plus scope, broad rules live in parents and concrete details in children, and Work Guidance and Verification stay empty when no standards or checks exist rather than being invented. Fifth, the placeholder line in the root AGENTS.md is replaced with the actual top-level index. Sixth, the skill reports every file created with its path and scope, every folder skipped and why, and every edited file with its recovery copy.

When to use - and when NOT to

Use it when the user says "init dox", "initialize DOX", "set up the DOX tree", "/dox" or "dox this project", wants a new or existing project to start from a documented agent-contract hierarchy rather than one monolithic instructions file, or asks where project-wide agent rules should live in a multi-folder repository.

For a single flat directory, a single-AGENTS.md or CLAUDE.md writer is enough; the tree only pays for itself once there are durable sub-boundaries. Run it on a clean worktree or review the diff before committing. It covers structure, not behaviour, and cannot know which folders are durable boundaries in an unfamiliar domain, so the user may need to prune or add after the first run.

Inputs and outputs

It needs network access for the one-time fetch of the DOX contract and write access to the project root and any folder that receives a child file; no account or token is required. For example, a request on a repo with src/, docs/, scripts/ and tests/ creates a root AGENTS.md with the project rules and child index, plus child files, and skips scripts/ because it is a single file with no local rules:

User request: "/dox this repo"
Created src/AGENTS.md, tests/AGENTS.md, docs/AGENTS.md

Output is Markdown files inside the project, with recovery paths recorded for any edits made after approval.

Source README

DOX is a hierarchy of AGENTS.md files that act as binding work contracts for the subtree they sit in: a root rail plus one file per durable folder, each with its own purpose, ownership, local contracts and an index of its children.

This skill bootstraps that tree for the current project in one pass. It fetches the official DOX contract, scans the real directory structure, and writes child files only where a folder is a durable boundary.

DOX itself is by Agent Zero and is not this skill's work. This skill is the bootstrapper: it installs the contract and builds the tree. It writes documentation files only; it does not change application code.

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.