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 skills add CrestApps/CrestApps.AgentSkills --skill crestapps-core-ai-agentsgit clone --depth 1 https://github.com/CrestApps/CrestApps.AgentSkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/crestapps/crestapps.agentskills/crestapps-core-ai-agents)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/crestapps-core-ai-agents"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/crestapps-core-ai-agents.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00026 | $0.00653 |
| Opus 5 | $0.00013 | $0.00327 |
| Sonnet 5 | $0.00005 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
crestapps-core-ai-agents 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 8d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrestApps.Core AI Agents - Prompt Templates
Create AI Agents
You are a CrestApps.Core expert. Generate code and guidance for specialized agent profiles in CrestApps.Core.
Guidelines
- Agents are standard
AIProfilerecords withType = AIProfileType.Agent. - Give every agent a strong
Descriptionbecause that is what the primary model uses for routing. - Use
OnDemandfor most agents andAlwaysAvailableonly when the agent should always be injected. - Link on-demand agents to chat profiles through
AgentInvocationMetadata. - By default a sub-agent runs with its tools disabled to prevent runaway recursion. Opt in per agent by setting
AgentMetadata.AllowToolInvocation = true; the agent then runs through the orchestrator with its configured tools enabled, guarded by a recursion-depth limit (AIInvocationContext.AgentInvocationDepth) that still blocks an agent from invoking other agents.
Agent Example
var agent = new AIProfile
{
Type = AIProfileType.Agent,
Name = "translator",
DisplayText = "Translator",
Description = "Translates text between languages.",
ChatDeploymentName = "gpt-4o-mini",
};
agent.Put(new AgentMetadata
{
Availability = AgentAvailability.OnDemand,
});
await profileManager.CreateAsync(agent);
Link the Agent to a Chat Profile
chatProfile.Put(new AgentInvocationMetadata
{
Names = ["translator", "code-reviewer"],
});
await profileManager.UpdateAsync(chatProfile);
Allow a Sub-Agent to Use Its Own Tools
By default a delegated agent runs with tools disabled. Enable them explicitly when the agent needs its configured tools during delegation:
agent.Put(new AgentMetadata
{
Availability = AgentAvailability.OnDemand,
AllowToolInvocation = true,
});
Even with AllowToolInvocation = true, the recursion-depth guard (AIInvocationContext.AgentInvocationDepth) prevents that agent from invoking further agents.
Code-Defined System Agents
Use IAIProfileProvider when an agent must be contributed by code instead of
stored as an editable AIProfile. A provider can return an
AIProfileType.Agent profile with AgentMetadata.IsSystem = true. System
agents can be AlwaysAvailable, exposed through A2A, and hidden from the
user-facing agent selection list. Register the provider with the AI services
using the standard IAIProfileProvider service registration pattern.
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.
- 8d ago First seen · 86 lines · 26 tokens per session scan A 495fa70dcffe
crestapps-core-ai-agents is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 10d ago), licensed MIT. It adds 26 tokens to every session and 653 once invoked, about $0.0001 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-30.
Other skills, from other repositories
powerpoint-cli
PowerPoint CLI automation skill for Windows presentations. Use when a coding agent needs token-efficient, scriptable, or unattended PowerPoint automation via pptcli commands. Best for CI/CD, scheduled jobs, batch processing, PowerShell workflows, and bulk deck edits. Supports slides, shapes, text frames, tables…
powerpoint-mcp
PowerPoint MCP Server skill for Windows presentation automation via a live PowerPoint desktop instance (COM/PIA). Use when an assistant needs rich MCP tools to create, open, build, format, and export PowerPoint (.pptx/.pptm) presentations — slides, shapes, text boxes, tables, native charts, images, audio, video…
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.
dotnet-debugging
Debug .NET applications using debug-mcp MCP tools — launch processes, set breakpoints, step through code, inspect variables, evaluate expressions, and analyze exceptions. Use this skill when debugging .NET/C# applications, investigating runtime behavior, diagnosing exceptions, inspecting object state, or performing…
release-notes
Writes user-facing release notes from a git commit range. Use when asked to draft release notes, a changelog entry, or "what's new" text for a release.
sast-fileupload
Detect insecure file upload vulnerabilities in a codebase using a three-phase approach: discovery (find all upload sites), batched verify (check extension bypass and related issues in parallel subagents, 3 sites each), and merge (consolidate batch results). Requires sast/architecture.md (run sast-analysis first).…