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 chrisgagne/grounded-forge --skill creating-applicationsgit clone --depth 1 https://github.com/chrisgagne/grounded-forgeWrote 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/chrisgagne/grounded-forge/creating-applications)<a href="https://agentmods.dev/skills/chrisgagne/grounded-forge/creating-applications"><img src="https://agentmods.dev/badge/skills/chrisgagne/grounded-forge/creating-applications.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.00131 | $0.06110 |
| Opus 5 | $0.00066 | $0.03055 |
| Sonnet 5 | $0.00026 | $0.01222 |
| Haiku 4.5 | $0.00013 | $0.00611 |
Grade A, and why
creating-applications 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 7d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Applications
An application is a compiled distribution: a corpus subset projected onto a task axis (optionally through a lens-set and a practitioner-role agent-set), bundled with a CLAUDE.md template and packaged at corpus.commons/{corpus}/apps/{profile}/. This skill scopes and assembles one application end-to-end.
The skill is the single user-facing entry point for creating an application. Internally it delegates to two sub-skills:
- Task-axis scoping. If no task spec exists at
corpus.commons/{corpus}/tasks/{task-slug}.md, invoke thecreating-tasksflow inline. The dialogue happens in this skill's conversation; the task spec drops at the right path; the skill continues onward without re-prompting the user. If a task spec already exists, skip. - Per-distillation projection. For each source named in the task spec, call
creating-distillationsonce. Pass G's applicability gate decides which distillations fire. Often dispatched as parallel sub-agents.
Between those two delegations, the skill does its own scaffolding work: distillation directory, distillation index (seeded from the task spec's practitioner questions and runtime listener grain), build profile in builds.yaml, package.json build script, build-profiles/{profile}.md CLAUDE.md template, and one agent file per agent declared in the task spec.
When to use
- A user wants a new application: a new compiled distribution shipping a slice of the corpus for a specific job. Phrasing varies: "create an AAR facilitator app", "build me a coaching tool from this corpus", "I want a distribution for incident review". Route all such asks here.
- A corpus reshape: the operator wants a new build profile that ships a different slice of the corpus to a different audience for a different task.
- After ingesting new sources that warrant their own application rather than just extending existing axes: e.g. a corpus of AAR-specific sources where the operator wants the AAR-shaped distribution as a first-class 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.
- 7d ago First seen · 250 lines · 0 tokens per session scan A 2e1757cb0a1a
creating-applications is a skill published in the GitHub repository chrisgagne/grounded-forge (7 stars, last pushed 17d ago), licensed MIT. It adds 131 tokens to every session and 6,110 once invoked, about $0.0007 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-31.
Other skills, from other repositories
warpp-workflow-authoring
Author WARPP workflows for Manifold as typed-port dataflow JSON. Use when a user asks to build, create, design, generate, or edit a Flow / workflow / automation / pipeline / DAG in Manifold, or mentions WARPP, workflow nodes, or the /flow builder. Covers the document format, port types and coercions, the builtin node…
manifold-api
Use when an agent needs to inspect or call the local Manifold HTTP API. Provides guidelines and scripts to filter specs before reading and handle payloads safely.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…