Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y @alipajand/[email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add io.github.alipajand-agent-readiness -- npx -y @alipajand/agent-readiness-mcp@0.1.2รันในเทอร์มินัล
{ "mcpServers": { "io.github.alipajand-agent-readiness": { "command": "npx", "args": [ "-y", "@alipajand/[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดA GitHub Action that checks how ready a repository is for AI coding agents (Claude Code, Cursor, Codex, Copilot, and similar). It bundles two deterministic engines:
context-audit: 'true', checks the instruction files themselves: placeholders, risky
directives, contradictions, stale commands, pasted secrets, hidden Unicode, and risky
Claude Code and MCP configuration such as bypassPermissions, hooks that run remote
scripts, or third-party API endpoints.It can fail the build below a score, block pull requests that lower the score, write a Markdown report, and post a summary comment on pull requests.
Both engines are bundled into the action at pinned commits, so nothing is downloaded or executed from a package registry at run time. There are no external API calls (other than the optional PR comment), no telemetry, and no LLM calls.
# .github/workflows/agent-readiness.yml
name: Agent Readiness Audit
on:
pull_request:
push:
branches: [main]
permissions:
contents: read
jobs:
audit:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
- uses: alipajand/agent-readiness-action@v1
name: Agent Readiness Audit
on:
pull_request:
push:
branches: [main]
permissions:
contents: read
jobs:
audit:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
- uses: alipajand/agent-readiness-action@v1
- uses: alipajand/agent-readiness-action@v1
with:
min-score: '70'
fail-on-threshold: 'true'
permissions:
contents: read
pull-requests: write
issues: write
steps:
- uses: actions/checkout@v7
- uses: alipajand/agent-readiness-action@v1
with:
comment-on-pr: 'true'
min-score: '70'
github-token: ${{ github.token }}
The action posts a single comment the first time and updates it on subsequent runs, so
there are no duplicate comments. It only updates a comment that starts with its hidden
marker and was written by a bot account, so pasting the marker into your own comment
does not make the action overwrite it. When commenting with a personal access token,
set comment-author to that account's login.
on:
pull_request:
jobs:
audit:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
with:
fetch-depth: 0 # the base commit must be available
- uses: alipajand/agent-readiness-action@v1
with:
baseline-ref: ${{ github.event.pull_request.base.sha }}
max-score-drop: '0'
The action audits the base commit in a temporary git worktree, reports the change (▼ -5 vs <sha>) in the log, job summary, and PR comment, and fails when the score drops by more than max-score-drop.
- uses: alipajand/agent-readiness-action@v1
with:
context-audit: 'true' # run the bundled agent-context-doctor
context-fail-on: 'high' # fail on risky instructions, secrets, hidden characters, ...
With context-audit, the action also runs agent-context-doctor on the same path. Its score and top issues appear in the log, job summary, and PR comment. It honors the audited repository's .acdrc.
steps:
- uses: actions/checkout@v7
- uses: alipajand/agent-readiness-action@v1
with:
output: 'docs/agent-readiness-report.md'
- uses: actions/upload-artifact@v7
with:
name: agent-readiness-report
path: docs/agent-readiness-report.md
- uses: alipajand/agent-readiness-action@v1
with:
repo-path: './packages/web'
Basic use (audit, log, and threshold check) only needs read access:
permissions:
contents: read
To post PR comments with comment-on-pr: "true", the job additionally needs
pull-requests: write and issues: write, and the step must pass a token through the
github-token input (or the GITHUB_TOKEN environment variable):
permissions:
contents: read
pull-requests: write
issues: write
PR comments are created and updated through GitHub's issue-comment API
(issues.listComments / issues.createComment / issues.updateComment), which is
why issues: write is included alongside pull-requests: write.
repo-path in the runner.
The engine is compiled into dist/index.js from the vendor/agent-readiness-kit
submodule, pinned to a reviewed commit.output is set, writes the kit's Markdown report inside repo-path.json is true, echoes the raw JSON to the log.baseline-ref is set, audits that commit in a temporary git worktree with the same bundled engine and computes the score change.comment-on-pr is true and the event is a pull_request, posts or updates a comment.job-summary is false).score < min-score (with fail-on-threshold) or the score dropped by more than max-score-drop.The action is meant to run on pull requests, including ones from contributors you don't
fully trust. Both engines are bundled from pinned submodules
(vendor/agent-readiness-kit, vendor/agent-context-doctor):
npx --yes agent-readiness-kit, which
fetched whatever package owned that name on npm. That name belongs to an unrelated
project. The audit engine is now bundled from a pinned commit of
agent-readiness-kit.repo-path and is never
written through a symlink. The audit does not write score history into the repository.::error:: or other commands. PR comments escape HTML and
keep file names in inline code.comment-author) is updated.See SECURITY.md to report a vulnerability, and docs/ARCHITECTURE.md for the module layout and trust boundaries.
A release has two separate steps: publishing an immutable version tag, and promoting it through the
floating major tag. Workflows that use @v1 change only at the second step.
Publish the version:
git submodule update --init so both engines under vendor/ are present.pnpm format:check, pnpm test, and pnpm typecheck.pnpm build.dist/ if it changed. CI fails when dist/ does not match the source.version in package.json and move the Unreleased notes in CHANGELOG.md under
the new version.main with its full version (for example v1.2.0) and push only that
tag: git tag -a v1.2.0 -m "agent-readiness-action 1.2.0", then git push origin v1.2.0. Never move or re-create a version tag.Promote it to v1 only after it has passed a real consumer workflow:
baseline-ref. Check that
the pull request run and the baseline comparison pass, and compare the scores, log, annotations,
and context findings with the previous version.git tag -f v1 v1.2.0^{}, then
git push -f origin v1.v1 resolves to that commit: git ls-remote origin refs/tags/v1 must print the
commit of v1.2.0^{}.Workflows that use @v1 pick up a release at step 8; pin a full commit SHA to review every change
first. The integrations (skill, plugin, MCP server) are versioned and tagged separately as
integrations-v<version> (docs/RELEASE-CHECKLIST.md); those tags never
move or depend on the action's v tags.
The same pinned engines are packaged for local use by AI coding agents. The scanner is read-only and offline; the agent that runs it may send the results to its model provider (security model):
agent-readiness-audit for Claude Code, Cursor, Codex, and other skill clients:
docs/integrations/SKILL-USAGE.mdagent-readiness:
docs/integrations/PLUGINS.md@alipajand/agent-readiness-mcp:
integrations/mcp-package/README.md; listed on
MCPRushSee docs/distribution/README.md for what is published where.
git submodule update --init # fetch the pinned engine sources
pnpm install
pnpm format # prettier (format:check in CI)
pnpm test # vitest unit tests
pnpm typecheck # tsc --noEmit
pnpm build # ncc bundle → dist/index.js
The built dist/ must be committed alongside source changes.
To move to a newer engine, check out the commit you want in vendor/agent-readiness-kit or
vendor/agent-context-doctor, run pnpm build, and commit both the submodule pointer and
dist/. Dependabot opens weekly submodule update PRs; those need a pnpm build commit
before CI passes.
See CONTRIBUTING.md for the full workflow and pull request guidelines.
MIT
Deterministic, read-only audits of repo readiness for AI coding agents and of agent context files.
{ "mcpServers": { "io.github.alipajand-agent-readiness": { "command": "npx", "args": [ "-y", "@alipajand/[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Agent Readiness ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-09 Deterministic, read-only audits of repo readiness for AI coding agents and of agent context files.