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/deploy-codeappnpx skills add Ramakrishnan24689/codeapps-toolkit --skill deploy-codeappgit 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.00036 | $0.02493 |
| Opus 5 | $0.00018 | $0.01247 |
| Sonnet 5 | $0.00007 | $0.00499 |
| Haiku 4.5 | $0.00004 | $0.00249 |
Grade A, and why
deploy-codeapp 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 — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Code App to Power Platform
Deploy your Code App to Power Platform with integrated validation, build checks, and deployment verification.
What This Skill Does
- Pre-deployment validation (codeapps-validator skill)
- Build quality check (build-lint-validator skill)
- Build application with asset path verification
- Deploy to Power Platform (
pac code push) - Post-deployment verification to ensure successful deployment
- Provide deployment summary with app URL and next steps
Usage
Deploy to Preferred Solution
/deploy-codeapp
Deploy to Specific Solution
/deploy-codeapp MySolutionName
Let Claude Invoke Automatically
Deploy my Code App to Power Platform
Push this app to production
Deploy to the "Marketing Apps" solution
Deployment Workflow
Phase 1: Pre-Deployment Validation
CRITICAL: Always validate BEFORE deploying to catch issues early.
Invoke codeapps-validator Skill
Automatically check:
- ✅ Package.json scripts configuration
- ✅ Port configuration (5173 and 8081)
- ✅ Dependencies installed
- ✅ Power Platform config (power.config.json valid)
- ✅ Vite config has
base: './'← CRITICAL for asset loading - ✅ Project structure complete
- ✅ TypeScript compilation succeeds
- ✅ ESLint compliance
If validation fails:
- Report specific issues found
- Attempt automatic fixes (e.g., add
base: './'to vite.config.ts) - Re-run validation
- STOP deployment if critical issues remain
Phase 2: Build Quality Check
Invoke build-lint-validator Skill
Verify code quality:
- ✅ TypeScript compiles without errors
- ✅ ESLint passes all rules
- ✅ No type mismatches
- ✅ No unused variables
- ✅ React Hook dependencies correct
If build validation fails:
- Report specific TypeScript/ESLint errors
- Guide user to fix errors
- STOP deployment until issues resolved
Phase 3: Build Application
npm run build
Expected Output:
vite v5.x.x building for production...
✓ XX modules transformed.
dist/index.html X.XX kB
dist/assets/index-xxxxx.js XX.XX kB
✓ built in X.Xs
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 · 436 lines · 36 tokens per session scan A 433f7f6cb3d0
deploy-codeapp is a skill published in the GitHub repository Ramakrishnan24689/codeapps-toolkit (5 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 2,493 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…