crestapps-core-data-storage

crestapps-core-data-storage is a skill for Claude Code from CrestApps/CrestApps.AgentSkills. It costs 168 tokens per session (2,178 once invoked), scanned A, original, MIT.

A guide for choosing and registering durable data storage in CrestApps.Core. It covers Entity Framework Core and YesSql, two libraries for saving application data, and explains how feature-specific stores connect to the main store.

In plain words
What is it for?
Use it when adding persistence to CrestApps.Core features, selecting Entity Framework Core or YesSql, configuring a SQLite or other backing store, or registering per-feature stores.
Why use it?
It prevents a feature from appearing to have storage configured when the underlying database store was never created. It also keeps each feature's storage requirements explicit instead of relying on an assumed global setup.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the crestapps-core plugin — 47 skills shipped together

Good fit Use it when adding persistence to CrestApps.Core features, selecting Entity Framework Core or YesSql, configuring a SQLite or other backing store, or registering per-feature stores.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/crestapps/crestapps.agentskills/crestapps-core-data-storage
Install

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.

Any agent
npx skills add CrestApps/CrestApps.AgentSkills --skill crestapps-core-data-storage
Clone the repo
git clone --depth 1 https://github.com/CrestApps/CrestApps.AgentSkills

Made for: Claude Code.

Or install crestapps-core, the plugin that ships this one along with the rest of its 47 skills.

Wrote 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.

agentmods badge for crestapps-core-data-storage

README.md
[![agentmods](https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/crestapps-core-data-storage/github.svg)](https://agentmods.dev/skills/crestapps/crestapps.agentskills/crestapps-core-data-storage)
Your own site
<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/crestapps-core-data-storage"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/crestapps-core-data-storage/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for crestapps-core-data-storage

Your own site · 80×15
<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/crestapps-core-data-storage"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/crestapps-core-data-storage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 168 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,178 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00168 $0.02178
Opus 5.5 $0.00067 $0.00871
Sonnet 5.5 $0.00034 $0.00436
Haiku 4.5 $0.00017 $0.00218

Measured yesterday against content hash c1169644f9b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

crestapps-core-data-storage 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 yesterday.

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.

plugins/crestapps-core/skills/crestapps-core-data-storage/SKILL.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CrestApps.Core Data Storage

You are a CrestApps.Core expert. Help the host choose a backend and register exactly the stores each enabled feature needs.

Guidelines

  • Choose Entity Framework Core when the host already uses EF Core or wants any EF relational provider. Choose YesSql when the host wants a document store with collections and map indexes (as Orchard Core does).
  • Register the backing store once on the root builder: .AddEntityCoreSqliteDataStore(...) / .AddEntityCoreDataStore(...), or .AddYesSqlDataStore(...). The per-feature Add*Stores() calls only select stores; they never create the DbContext or IStore.
  • Call the store method on every feature builder you enable. One call does not cover other features.
  • Without a store package, connections and deployments come only from configuration and ISearchIndexProfileStore falls back to a null store, but nothing registers IAIProfileStore, the chat session stores, or the ChatInteraction catalog. Register a store before resolving IAIProfileManager, chat sessions, or Chat Interactions.
  • Every write path needs a commit boundary (IStoreCommitter); see crestapps-core-foundations.
  • Create the schema before serving requests: InitializeEntityCoreSchemaAsync() for EF Core, or the Create*IndexSchemaAsync extensions for YesSql.

Entity Framework Core

using CrestApps.Core;
using CrestApps.Core.AI;
using CrestApps.Core.AI.A2A;
using CrestApps.Core.AI.Chat;
using CrestApps.Core.AI.Documents;
using CrestApps.Core.AI.Documents.OpenXml;
using CrestApps.Core.AI.Documents.Pdf;
using CrestApps.Core.AI.Mcp;
using CrestApps.Core.AI.OpenAI;
using CrestApps.Core.Data.EntityCore;

Directory.CreateDirectory(Path.Combine(builder.Environment.ContentRootPath, "App_Data"));

builder.Services.AddCrestAppsCore(crestApps => crestApps
    .AddAISuite(ai => ai
        .AddEntityCoreStores()
        .AddOpenAI()
        .AddChatInteractions(chat => chat.AddEntityCoreStores())
        .AddDocumentProcessing(documents => documents
            .AddEntityCoreStores()
            .AddOpenXml()
            .AddPdf())
        .AddAIMemory(memory => memory.AddEntityCoreStores())
        .AddPersonas(personas => personas.AddEntityCoreStores())
        .AddToolInstances(tools => tools.AddEntityCoreStores())
        .AddA2AClient(a2a => a2a.AddEntityCoreStores())
        .AddMcpClient(mcp => mcp.AddEntityCoreStores())
        .AddMcpServer(mcp => mcp.AddEntityCoreStores()))
    .AddIndexingServices(indexing => indexing.AddEntityCoreStores())
    .AddEntityCoreSqliteDataStore(
        $"Data Source={Path.Combine(builder.Environment.ContentRootPath, "App_Data", "crestapps.db")}"));

// Features registered on IServiceCollection
builder.Services.AddCoreWebCrawlerStoresEntityCore();
builder.Services.AddCoreFileSourceStoresEntityCore();

var app = builder.Build();
await app.Services.InitializeEntityCoreSchemaAsync();

Read the full file on GitHub · 131 lines

Changes

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.

  1. yesterday Changed · +71 lines · +142 tokens per session c1169644f9b7
  2. 1mo ago First seen · 60 lines · 26 tokens per session scan A 131704cdb3e4

Subscribe to this mod's changes

crestapps-core-data-storage is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed yesterday), licensed MIT. It adds 168 tokens to every session and 2,178 once invoked, about $0.0007 per session on Opus 5.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.

Related

Other skills, from other repositories