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-entitycore-storesnpx skills add CrestApps/CrestApps.AgentSkills --skill crestapps-core-entitycore-storesgit 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-entitycore-stores)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/crestapps-core-entitycore-stores"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/crestapps-core-entitycore-stores.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 | $0.00027 | $0.01053 |
| Opus 5 | $0.00014 | $0.00526 |
| Sonnet 5 | $0.00005 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade A, and why
crestapps-core-entitycore-stores 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 5d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrestApps.Core EntityCore Stores - Prompt Templates
Configure Entity Framework Core Persistence
You are a CrestApps.Core expert. Generate accurate Entity Framework Core persistence guidance using CrestApps.Core.Data.EntityCore.
Rules
- Register
AddEntityCoreDataStore(...)orAddEntityCoreSqliteDataStore(...)on the rootCrestAppsCoreBuilder. They registerCrestAppsEntityDbContextandEntityCoreStoreCommitter. AddEntityCoreStores()selects feature stores. It is separate from registering theDbContext.EntityCoreStoreCommittercallsSaveChangesAsync()only whenChangeTracker.HasChanges()is true. Use the MVC, Minimal API, SignalR, or explicit background-scope commit boundary.EntityCoreDataStoreOptions.TablePrefixdefaults to"CA_".EnforceNamedSourceUniquenessdefaults tofalse; turn it on only after removing duplicates and applying an EF Core migration.- Extend the model by implementing
ICrestAppsModelConfigurer; do not subclass the sealedCrestAppsEntityDbContext.
builder.Services.AddControllersWithViews()
.AddCrestAppsStoreCommitterFilter();
builder.Services.AddCrestAppsCore(crestApps => crestApps
.AddAISuite(ai => ai
.AddEntityCoreStores()
.AddChatInteractions(chat => chat.AddEntityCoreStores())
.AddDocumentProcessing(documents => documents.AddEntityCoreStores())
.AddAIMemory(memory => memory.AddEntityCoreStores())
)
.AddIndexingServices(indexing => indexing.AddEntityCoreStores())
.AddEntityCoreSqliteDataStore(
$"Data Source={Path.Combine(builder.Environment.ContentRootPath, "App_Data", "crestapps.db")}")
);
For another EF provider, configure it directly:
builder.Services.AddCrestAppsCore(crestApps => crestApps
.AddEntityCoreDataStore(
options => options.UseNpgsql(connectionString),
store => store.TablePrefix = "App_")
);
Per-Feature Registration
The builder extensions are available on CrestAppsAISuiteBuilder, CrestAppsChatInteractionsBuilder, CrestAppsDocumentProcessingBuilder, CrestAppsAIMemoryBuilder, CrestAppsIndexingBuilder, CrestAppsA2AClientBuilder, CrestAppsMcpClientBuilder, CrestAppsMcpServerBuilder, and CrestAppsAIToolInstancesBuilder.
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.
- 5d ago First seen · 60 lines · 27 tokens per session scan A a645d33ab445
crestapps-core-entitycore-stores is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 7d ago), licensed MIT. It adds 27 tokens to every session and 1,053 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
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.
testing
Run and troubleshoot tests for DBHub, including unit tests, integration tests with Testcontainers, and database-specific tests. Use when asked to run tests, fix test failures, debug integration tests, troubleshoot Docker/database container issues, or add new tests. Also use when verifying code changes work correctly…
dv-query
Bulk reads, multi-page iteration, and analytics over Dataverse data. Use when the user wants to read, list, filter, aggregate, group, join, or analyze records — including pandas DataFrame workflows and notebook exploration.
solr-semantic-search
To build Solr phrase-tagging semantic search: concept tagging, taxonomy, graph paths.
solr-schema
To design and audit Solr schemas: field types, analyzers, docValues, solrconfig.
npgsqlrest
Build and modify REST APIs with NpgsqlRest — exposing PostgreSQL as HTTP endpoints from two sources (database functions/procedures/tables/views, and plain .sql files), driven by SQL comment annotations (no C# needed). Use when working in an NpgsqlRest project: writing or changing endpoint SQL (functions or .sql…