Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/ramakrishnan24689/codeapps-toolkit/codeapps-validatornpx skills add Ramakrishnan24689/codeapps-toolkit --skill codeapps-validatorgit clone --depth 1 https://github.com/Ramakrishnan24689/codeapps-toolkitWhat 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 | $0.00042 | $0.04086 |
| Opus 5 | $0.00021 | $0.02043 |
| Sonnet 5 | $0.00008 | $0.00817 |
| Haiku 4.5 | $0.00004 | $0.00409 |
Grade A, and why
codeapps-validator 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 — 622 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeApps Validator Skill
Purpose
Systematically validate Power Platform Code Apps projects to ensure proper configuration, structure, and readiness for development or deployment. This skill validates all critical aspects of a CodeApps project including npm scripts, port configuration, dependencies, and Power Platform integration.
When to Use This Skill
ALWAYS use after:
- Initial project setup (after Step 1 in workshop)
- Adding data sources or connectors
- Modifying package.json scripts
- Before deployment to Power Platform
- When troubleshooting configuration issues
Use to validate:
- package.json dev scripts configuration
- Port assignments (5173 for Vite, 8081 for pac code run)
- Required dependencies installation
- Power Platform configuration (power.config.json)
- Project structure and folders
- TypeScript compilation success
- ESLint compliance
Validation Framework
This skill performs 8 critical checks:
1. Package.json Scripts Validation
Ensures dev scripts are properly configured for dual-server setup.
2. Port Configuration Check
Validates correct port usage (5173 for Vite, 8081 for pac code run).
3. Dependencies Validation
Confirms all required packages are installed.
4. Power Platform Configuration Check
Verifies power.config.json exists and has proper structure.
5. Vite Configuration Check (CRITICAL)
Validates vite.config.ts has base: './' for correct asset paths in deployment.
6. Project Structure Validation
Ensures required folders and files exist.
7. TypeScript Compilation Check
Validates code compiles without errors.
8. ESLint Compliance Check
Verifies code passes linting rules.
Validation Process
Step 1: Validate package.json Scripts
Check for proper dev script configuration:
# Read package.json
cat package.json | grep -A 5 '"scripts"'
Required scripts:
{
"scripts": {
"dev": "concurrently \"npm:dev:vite\" \"npm:dev:pac\"",
"dev:vite": "vite --port 5173",
"dev:pac": "pac code run --port 8081 --appUrl http://localhost:5173",
"build": "tsc && vite build",
"lint": "eslint . --ext ts,tsx"
}
}
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 · 622 lines · 42 tokens per session scan A a19e711b50c6
codeapps-validator is a skill published in the GitHub repository Ramakrishnan24689/codeapps-toolkit (5 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 4,086 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…