AgentRC prepares repositories for AI coding agents by analyzing their code and generating project-specific instructions, evaluations, and development configuration. It is used through a CLI, VS Code extension, or CI pipeline to measure AI readiness, keep context useful, and detect drift; the catalogue entries support these repository-preparation workflows.
Borrowing it
Nothing to install: this file belongs to microsoft/agentrc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/agentrc/main/.github/prompts/align-cli-webapp-reports.prompt.mdgit clone --depth 1 https://github.com/microsoft/agentrcWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/microsoft/agentrc/align-cli-webapp-reports)<a href="https://agentmods.dev/commands/microsoft/agentrc/align-cli-webapp-reports"><img src="https://agentmods.dev/badge/commands/microsoft/agentrc/align-cli-webapp-reports.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00027 | $0.01681 |
| Opus 5 | $0.00014 | $0.00840 |
| Sonnet 5 | $0.00005 | $0.00336 |
| Haiku 4.5 | $0.00003 | $0.00168 |
Grade A, and why
align-cli-webapp-reports scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are debugging consistency between two readiness report outputs for the AgentRC project:
- CLI visual report — generated by
npm run dev -- readiness --visualfrom the repo root (produces an HTML file) - Webapp report — rendered by the local dev server at
http://localhost:3000/{owner}/{repo}
Both should produce identical results for the same repository because they share the same core engine (packages/core/src/services/readiness.ts). In practice they can diverge due to rendering differences or scoring logic bugs.
Architecture Reference
Shared Core (source of truth for checks)
packages/core/src/services/readiness.ts— All criteria definitions,countStatus(),buildCriteria(),buildExtras(), pillar/level aggregation- Criteria scopes:
repo(always),app(per-application),area(only with--per-area) countStatus()excludes skipped checks from the denominator when computing pillar pass/total- Extras (bonus checks) are not scored — they don't affect levels or totals
CLI Rendering
packages/core/src/services/visualReport.ts— Generates the standalone HTML reportcalculateAiToolingData()— Aggregates AI criteria across repos (counts all including skipped in the hero display)- Total checks:
report.pillars.reduce((s, p) => s + p.total, 0) - Does not render bonus/extras section in HTML output
Webapp Backend
webapp/backend/src/services/scanner.js— Clones repo, callsrunReadinessReport()from@agentrc/corewebapp/backend/src/routes/scan.js—POST /api/scanendpoint- Returns the raw
ReadinessReportJSON (same shape as CLI) - Uses
@agentrc/coreas afile:../../packages/coredependency — always uses local source code
Webapp Frontend
webapp/frontend/src/report.js— Independent rendering implementation (NOT shared with CLI)buildHero()— Total fromreport.pillars.reduce((s, p) => s + p.total, 0)buildAiToolingHero()— Renders all AI criteria (including skipped) with pass/total countbuildPillarDetails()— Shows per-pillar expandable cards- Does render bonus checks section (unlike CLI)
- Has Service Information section (policy chain, engine signals) — CLI doesn't
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 162 lines · 27 tokens per session scan A 7145300a2865
align-cli-webapp-reports is a command published in the GitHub repository microsoft/agentrc (1,052 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,681 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.