mkdir -p ~/.codex/skills/duoattest
curl -fsSL https://duola.manyaitool.com/skills/duoattest/SKILL.md \
-o ~/.codex/skills/duoattest/SKILL.mdDUOATTEST AGENT SKILL
Put trust in the delivery path.
Keep the verdict independent.
Install once. From then on, every coding task automatically prepares its task contract, evidence readiness, PR binding, and Head-update revalidation. You do not need to mention DuoAttest again, and the Agent never controls the verdict.
Your coding Agent can manage setup and evidence readiness, but it can never issue a green result. DuoAttest independently runs the final Base/Head proof and binds the certificate to the exact Commit; the Dashboard remains a read-only evidence center.
Put the Skill where your Agent reads skills.
Download the file into a duoattest skill directory. Then use one natural language instruction from inside any GitHub repository.
mkdir -p .claude/skills/duoattest
curl -fsSL https://duola.manyaitool.com/skills/duoattest/SKILL.md \
-o .claude/skills/duoattest/SKILL.mdGive the downloaded SKILL.md to any Agent that can run commands and call HTTP or MCP tools. The protocol is client-independent.
Connect this repository to DuoAttest and confirm verification is working.
The Agent opens one GitHub consent page. After approval it resumes automatically; no token copying, YAML editing or Dashboard setup. This is the only time you need to ask for DuoAttest by name.
01Agent detects the repository
Reads the Git remote, languages, tests and existing CI without asking the user.
02User approves once
GitHub confirms the account and exact repository scope. No secret is pasted.
03Agent finishes setup
Creates or reuses the setup PR, checks status and reports the next concrete action.
04Every later coding task is automatic
The Agent prepares evidence before the PR, binds it after creation, and refreshes it whenever Head changes. DuoAttest independently verifies the result in your Runner.