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/crestapps/crestapps.agentskills/crestapps-core-chatnpx skills add CrestApps/CrestApps.AgentSkills --skill crestapps-core-chatgit 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-chat)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/crestapps-core-chat"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/crestapps-core-chat.svg" alt="Measured on agentmods" height="20"></a>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.00020 | $0.00725 |
| Opus 5 | $0.00010 | $0.00362 |
| Sonnet 5 | $0.00004 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
crestapps-core-chat 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 6d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrestApps.Core Chat - Prompt Templates
Build a Chat Completion Loop
You are a CrestApps.Core expert. Generate code and guidance for deployment-aware chat completions, streaming, and orchestration loops.
Guidelines
- CrestApps.Core exposes
IAICompletionService, notIChatCompletionService; it returns Microsoft.Extensions.AIChatResponseandChatResponseUpdatevalues. - Register the AI suite and at least one provider, then configure a Chat-capable deployment and connection.
- Resolve an
AIDeploymentthroughIAIDeploymentManagerrather than constructing provider clients in application code. - Use
CompleteAsync(...)for one result andCompleteStreamingAsync(...)withawait foreachfor incremental output. - Pass an
AICompletionContextfor system instructions, sampling settings, deployment names, and tool choices. - Use
IOrchestrator.ExecuteStreamingAsync(...)when the request needs planning, tool scoping, or an iterative agent loop. - This skill is the completion and orchestration surface.
crestapps-core-chat-interactionsis the persisted session, history, handler-routing, and SignalR interaction feature. - The direct completion guidance here corresponds to the AI core and orchestration documentation. The
/docs/core/chattopic documentscrestapps-core-chat-interactions, not this direct completion loop.
Registration
builder.Services.AddCrestAppsCore(crestApps => crestApps
.AddAISuite(ai => ai
.AddOpenAI()
)
);
Configure an OpenAI connection and a deployment whose Purpose includes AIDeploymentPurpose.Chat.
Stream a Response
using System.Runtime.CompilerServices;
using CrestApps.Core.AI.Completions;
using CrestApps.Core.AI.Deployments;
using CrestApps.Core.AI.Models;
using Microsoft.Extensions.AI;
namespace MyApp;
public sealed class ChatCompletionLoop
{
private readonly IAICompletionService _completionService;
private readonly IAIDeploymentManager _deploymentManager;
public ChatCompletionLoop(
IAICompletionService completionService,
IAIDeploymentManager deploymentManager)
{
_completionService = completionService;
_deploymentManager = deploymentManager;
}
public async IAsyncEnumerable<ChatResponseUpdate> StreamAsync(
string prompt,
[EnumeratorCancellation] CancellationToken cancellationToken = default)
{
var deployment = await _deploymentManager.ResolveOrDefaultAsync(
AIDeploymentPurpose.Chat,
cancellationToken: cancellationToken)
?? throw new InvalidOperationException("No Chat deployment is configured.");
var context = new AICompletionContext
{
SystemMessage = "You are a concise support assistant.",
Temperature = 0.2f,
};
await foreach (var update in _completionService.CompleteStreamingAsync(
deployment,
[new ChatMessage(ChatRole.User, prompt)],
context,
cancellationToken))
{
yield return update;
}
}
}
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.
- 6d ago First seen · 91 lines · 20 tokens per session scan A 1245f6cb97f3
crestapps-core-chat is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 8d ago), licensed MIT. It adds 20 tokens to every session and 725 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
prepare-release
Prepare a new release for the C# MCP SDK. Assesses Semantic Versioning level (PATCH/MINOR/MAJOR), bumps the version, runs ApiCompat and ApiDiff, reviews documentation, updates changelogs, drafts release notes, and creates a pull request with all release artifacts. Use when asked to prepare a release, start a release…
publish-release
Publish a GitHub release for the C# MCP SDK after a prepare-release PR has been merged. Refreshes release notes to include any PRs merged since preparation, warns about version or breaking change impacts from late-arriving PRs, and creates a draft GitHub release. Use when asked to publish a release, finalize a…
verify-release
Verify a published release of the C# MCP SDK. Monitors the Release and Publish Docs workflows triggered by publishing a GitHub release, confirms the packages are listed on NuGet.org, and confirms the versioned documentation site reflects the release. Use when asked to verify a release, check whether a release…
bump-version
Assess and bump the SDK version using Semantic Versioning 2.0.0. Evaluates queued changes to recommend PATCH/MINOR/MAJOR, updates src/Directory.Build.props, and creates a pull request. Owns the SemVer assessment logic shared by prepare-release and publish-release. Use when asked to bump the version, assess the…
breaking-changes
Audit pull requests for breaking changes in the C# MCP SDK. Examines PR descriptions, review comments, and diffs to identify API and behavioral breaking changes, then reconciles labels with user confirmation. Use when asked to audit breaking changes, check for breaking changes, or review a set of PRs for breaking…
run-conformance-from-branch
Run MCP conformance tests in the C# SDK against a conformance branch (including forks) instead of the published npm version, then restore pinned dependencies.