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-profilesgit 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-profiles)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/crestapps-core-ai-profiles"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/crestapps-core-ai-profiles.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.00029 | $0.00405 |
| Opus 5 | $0.00015 | $0.00202 |
| Sonnet 5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
crestapps-core-ai-profiles 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.
What it actually says
CrestApps.Core AI Profiles - Prompt Templates
Create Reusable AI Profiles
You are a CrestApps.Core expert. Generate code and guidance for AI Profiles in CrestApps.Core.
Guidelines
- Use Chat Interactions for fast ad hoc validation.
- Move to AI Profiles when the experience needs stable reusable behavior.
- Keep model choice in deployments and behavior choice in the profile.
- Use profile descriptions for agent scenarios and routing decisions.
- Let profiles own prompt behavior, tools, retrieval, memory, and post-session behavior.
AI Profile vs Other Building Blocks
| Concept | Question it answers |
|---|---|
| Connection | How do I talk to a provider |
| Deployment | Which model should run |
| Chat Interactions | Let me test this setup quickly |
| AI Profile | How should this AI experience behave |
Typical Lifecycle
- Create a provider connection.
- Create one or more deployments.
- Verify the deployment with Chat Interactions.
- Create an AI Profile once the behavior should be reusable.
- Attach tools, documents, data sources, or memory.
Example Agent Profile
var profile = new AIProfile
{
Type = AIProfileType.Agent,
Name = "code-reviewer",
DisplayText = "Code Reviewer",
Description = "Reviews code for bugs, security issues, and correctness.",
ChatDeploymentName = "gpt-4o",
};
profile.Put(new AgentMetadata
{
Availability = AgentAvailability.OnDemand,
});
await profileManager.CreateAsync(profile);
Design Guidance
- Use profiles to capture reusable behavior and lifecycle rules.
- Use separate chat and utility deployments when the workflow benefits from it.
- Keep system instructions, tools, and retrieval aligned to one purpose.
- Prefer multiple focused profiles over one overloaded profile.
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 · 63 lines · 29 tokens per session scan A bb679c2b251a
crestapps-core-ai-profiles is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 10d ago), licensed MIT. It adds 29 tokens to every session and 405 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).…