chant with a coding agent
llms.txt lists every page for an agent
For a team that hands infrastructure work to a coding agent: one prompt sets chant up, and the project carries the playbooks and tools the agent reads.
Works
- A copy-paste setup prompt on Agents Start Here, which installs a lexicon and scaffolds the project
chant initwrites askills/directory of playbooks from each lexicon and a.mcp.jsonthat registers the chant MCP server- A page that describes a task can carry a prompt for the agent under its title, and
llms.txtlists every page chant audit --agentschecks the agent setup on the machine: instruction files, MCP servers, skills, plugins and tool permissions
Differs
By forge
--generate githubwrites the pull-request workflow under.github/workflows/, run onpull_requestand onpushto the target branch.- Both jobs use the job's own
github.token. On a pull request from a fork that token is read-only, so the plan note and the status are not posted.
--generate gitlabwrites.gitlab-ci.yml, andapplyruns one at a time per environment throughresource_group.- A CI job token cannot write merge request notes, so set a project access token with the
apiscope as the masked variableCHANT_FORGE_TOKEN.
--generate forgejowrites the GitHub workflow in the Forgejo dialect under.forgejo/workflows/: the runner label, action references by URL, and nopermissionsblock.- Forgejo workflows are GitHub-dialect, so
chant auditapplies its GitHub rules to them.
First step
Or paste the prompt from Agents Start Here and let the agent pick the lexicon.
npm install --save-dev @intentius/chant-lexicon-awsnpx chant init . --lexicon awsShow the whole prompt
Set up chant in this repository.
Read https://intentius.io/chant/llms.txt first, then
https://intentius.io/chant/agents/ and follow it.
Stop when `npx chant build` and `npx chant lint` pass, and open a pull request with the result.
Never deploy to a real cloud account or shared environment (with `chant run`, `chant components` or a platform's own CLI), approve (a pull request review, `chant approve` or `chant run approve`), override a policy denial (`chant approve policy-override`), or merge; never cut or publish a release (`chant release cut --yes` or `chant release publish`), push or delete a `ci/*` tag (`chant ci tick` pushes them), or change the value of an existing flag; never touch `.chant/allowed_signers` or `chant/lifecycle`.Proof
Example projects in the chant repository for this room, each with a README that has the commands to run it.
| Example | Where |
|---|---|
getting-started | examples/getting-started |
alert-triage | examples/alert-triage |
Then read
- Tasks
- Agents Start Here
- Background
- Agent IntegrationOps as Teammates
- Reference
- chant serve mcpchant audit