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/fix-codeapp-issuenpx skills add Ramakrishnan24689/codeapps-toolkit --skill fix-codeapp-issuegit 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.00046 | $0.01664 |
| Opus 5 | $0.00023 | $0.00832 |
| Sonnet 5 | $0.00009 | $0.00333 |
| Haiku 4.5 | $0.00005 | $0.00166 |
Grade A, and why
fix-codeapp-issue 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Code Apps Issues
Diagnose and fix common Power Apps Code Apps issues with guided troubleshooting and automated repairs.
What This Skill Does
- Diagnoses common CodeApps issues based on symptoms
- Provides step-by-step troubleshooting guidance
- Attempts automated fixes when possible
- Validates fixes with integrated validation
- Provides prevention tips
Common Issues & Solutions
Issue 1: 404 Errors for Assets (Blank Screen After Deployment)
Symptoms:
- Deployed app shows blank screen
- Console shows:
GET .../assets/index-xxx.js net::ERR_ABORTED 404 - MIME type error:
Refused to apply style ... MIME type ('application/json')
Root Cause: Missing base: './' in vite.config.ts
Automated Fix:
// Check vite.config.ts
const config = await read('vite.config.ts');
if (!config.includes("base: './'")) {
// Add base: './' to config
const updated = config.replace(
'export default defineConfig({',
`export default defineConfig({\n base: './',`
);
await write('vite.config.ts', updated);
console.log('✅ Added base: "./" to vite.config.ts');
// Rebuild
await exec('npm run build');
// Suggest redeploy
console.log('💡 Run: pac code push');
}
Issue 2: System-Managed Field Error (Dataverse)
Symptoms:
PrimitiveValue node with non-null value was found... 'ownerid'- Create/update operations fail
Root Cause: Sending system-managed fields (ownerid, statecode, timestamps, primary key)
Fix: Review service layer and remove system-managed fields:
// ❌ WRONG
const payload = {
name: dto.name,
ownerid: '', // Remove this
statecode: 0, // Remove this
};
// ✅ CORRECT
const payload = {
name: dto.name,
// Dataverse sets ownerid, statecode automatically
};
Issue 3: Boolean Field Type Mismatch
Symptoms:
Cannot convert the literal '1' to expected type 'Edm.Boolean'- Update operations fail with Boolean fields
Root Cause: Generated types suggest numeric (0|1) but Dataverse expects boolean
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 · 307 lines · 46 tokens per session scan A be9148898807
fix-codeapp-issue is a skill published in the GitHub repository Ramakrishnan24689/codeapps-toolkit (5 stars, last pushed 6mo ago), licensed MIT. It adds 46 tokens to every session and 1,664 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…