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/gen-servicenpx skills add Ramakrishnan24689/codeapps-toolkit --skill gen-servicegit 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.00035 | $0.03099 |
| Opus 5 | $0.00017 | $0.01550 |
| Sonnet 5 | $0.00007 | $0.00620 |
| Haiku 4.5 | $0.00003 | $0.00310 |
Grade A, and why
gen-service 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 2d ago.
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.
Generate Service Layer Wrapper
Generate a service layer that wraps generated Dataverse or connector services with best practices, error handling, and data transformations.
What This Skill Does
- Reads generated model and service files from
src/generated/ - Creates domain model types (DTO interfaces)
- Generates service class with CRUD operations
- Implements proper error handling and user-friendly messages
- Handles CodeApps-specific issues (system-managed fields, Boolean type mismatches)
- Provides data transformation methods (API → domain model)
Usage
/gen-service dataverse account
/gen-service dataverse todos
/gen-service connector office365users
Service Layer Pattern
For Dataverse Tables
Generated Service (src/generated/services/AccountsService.ts):
- Low-level API calls
- Auto-generated types
- No business logic
- DO NOT MODIFY (regenerated when schema changes)
Custom Service (src/features/accounts/services/AccountService.ts):
- Wraps generated service
- Business logic and validation
- User-friendly error messages
- Data transformations
- Safe to modify (your code)
For Connectors
Similar pattern but adapted for connector-specific operations (methods instead of CRUD).
Templates
This skill uses production-ready templates that demonstrate all best practices:
- templates/dataverse-service.template.ts - Complete Dataverse service with CRUD operations, Context API integration
- templates/connector-service.template.ts - Connector service wrapper pattern
- examples/todo-service-example.ts - Complete CRUD example with Dataverse
- examples/context-usage-example.ts - Context API patterns (user filtering, environment detection)
- examples/metadata-usage-example.ts - getMetadata() patterns (dynamic forms, localized labels)
- examples/sharepoint-operations-example.ts - SharePoint-specific patterns (expanded objects, getReferencedEntity)
How to use templates: Read the template file for the pattern, then generate adapted code based on the actual generated files you discover.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 436 lines · 0 tokens per session scan A 4dffbb0c1317
gen-service is a skill published in the GitHub repository Ramakrishnan24689/codeapps-toolkit (6 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 3,099 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…