@khalilzhang0825/steadyagent
AAGENTS.md - SteadyAgent Codex Guide
Install
agr install @khalilzhang0825/steadyagent --target claudeWrites 1 file into .claude/skills/, pinned to git-7ce0de5d.
- .claude/skills/steadyagent/AGENTS.md
Document
AGENTS.md - SteadyAgent Codex Guide
This file gives Codex a compact project map for contributing to SteadyAgent.
Project Intent
SteadyAgent is a local-first harness for AI coding agents. It packages concise instructions, progressive rules, validation scripts, lifecycle hook examples, and release evidence so agent-assisted development is easier to scope, verify, review, and recover.
Working Rules
- Keep changes scoped to the requested workflow, tool, template, or documentation surface.
- Read the nearest project guide, relevant docs, and directly touched scripts before editing.
- Prefer deterministic scripts, tests, and hooks over longer instructions when behavior must be enforced.
- Preserve the public release surface: no private paths, local credentials, unpublished plans, or maintainer-only notes.
- Keep English as the default public surface; update the paired Chinese docs when user-facing behavior changes.
- Use
rgorrg --filesfor repository search.
Validation
Run the smallest relevant gate before committing:
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\tools\validate-release-readiness.ps1
Focused checks:
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\tools\validate-phase3.ps1
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\tools\validate-runtime-slice.ps1
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\tools\test-agent-hooks.ps1
Use -AllowDirty with validate-release-readiness.ps1 only while reviewing an intentional work-in-progress tree.
Release Discipline
- Do not publish, retag, or rewrite remote history without explicit maintainer approval.
- Treat
v1.0.0and later releases as audited artifacts: clean history, reproducible validation, and clear release notes. - Use docs/github-publication-runbook.md for public release steps.
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-7ce0de5d388b2026-08-04