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/init-codeappnpx skills add Ramakrishnan24689/codeapps-toolkit --skill init-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.00037 | $0.01665 |
| Opus 5 | $0.00018 | $0.00833 |
| Sonnet 5 | $0.00007 | $0.00333 |
| Haiku 4.5 | $0.00004 | $0.00167 |
Grade A, and why
init-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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Code App Project
Initialize a new Power Apps Code App with proper configuration for development and deployment.
What This Skill Does
- Creates project from official Microsoft template
- Configures package.json for dual-server development (Vite + pac code run)
- Sets up vite.config.ts with
base: './'(critical for deployment) - Installs all dependencies including concurrently
- Runs pac code init to register with Power Platform
- Validates entire setup with integrated validation
Usage
/init-codeapp my-app-name
or let Claude invoke automatically:
Initialize a new Code App called todo-app
Workflow
Step 1: Check Prerequisites
Verify required tools are installed:
# Check Node.js
node --version
# Check Power Platform CLI
pac --version
# Check Git
git --version
If any tools are missing, inform the user and provide installation links:
- Node.js: https://nodejs.org/
- Power Platform CLI: https://learn.microsoft.com/power-platform/developer/cli/introduction
- Git: https://git-scm.com/
Step 2: Authentication Check
# Check if user is authenticated
pac auth list
If not authenticated or environment not selected:
pac auth create
pac env select --environment <environmentId>
Step 3: Create Project from Template
# Use official Microsoft template
npx degit github:microsoft/PowerAppsCodeApps/templates/vite $ARGUMENTS[0]
cd $ARGUMENTS[0]
Naming Best Practice: For shared environments, suggest including username:
Suggested name: $ARGUMENTS[0]-{username}
Would you like to use this naming pattern? (Prevents conflicts in shared environments)
Step 4: Install Dependencies
npm install
# Install required dev dependencies
npm install --save-dev concurrently
# Install recommended dependencies
npm install @tanstack/react-query
Step 5: Configure package.json Scripts
Check if scripts need updating:
cat package.json | grep -A 5 '"scripts"'
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 · 277 lines · 37 tokens per session scan A babd37010295
init-codeapp is a skill published in the GitHub repository Ramakrishnan24689/codeapps-toolkit (5 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 1,665 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…