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/xobotyi/cc-foundry/framenpx skills add xobotyi/cc-foundry --skill framegit clone --depth 1 https://github.com/xobotyi/cc-foundryWrote 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/xobotyi/cc-foundry/frame)<a href="https://agentmods.dev/skills/xobotyi/cc-foundry/frame"><img src="https://agentmods.dev/badge/skills/xobotyi/cc-foundry/frame.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.00046 | $0.01743 |
| Opus 5 | $0.00023 | $0.00872 |
| Sonnet 5 | $0.00009 | $0.00349 |
| Haiku 4.5 | $0.00005 | $0.00174 |
Grade A, and why
frame 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.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frame
Structure implementation as vertical slices — each phase crosses all affected layers end-to-end, producing a testable integrated path. Phase 1 is the tracer bullet: the thinnest possible slice wired through every layer. Models default to horizontal plans (all DB, then all API, then all UI); this skill enforces vertical structure that cannot be prompted away.
Horizontal (wrong — layer by layer):
- Phase 1: All DB — notification tables, preferences, delivery log
- Phase 2: All service — email sender, in-app dispatcher, preference resolver
- Phase 3: All API — notification endpoints, preference endpoints
- Phase 4: All UI — notification center, preference panel, toast
By Phase 4, the agent has generated hundreds of lines across every layer. Integration reveals the notification table schema assumed a delivery model the service layer doesn't support. Fix cascades through all layers — most work is discarded.
Vertical (correct — slice by slice):
- Phase 1 (tracer bullet): Email notification, one path — table, service, endpoint, toast. Validates the full stack.
- Phase 2: In-app notifications — extends schema, adds dispatcher, wires notification center.
- Phase 3: User preferences — preference table, resolver, settings endpoint, preference panel.
Schema error surfaces in Phase 1, not Phase 4. Each phase is testable and deployable independently.
Prerequisites
Locate the inputs:
- Alignment — check conversation context first; fall back to
design-docs/NN-name.alignment.md; if absent, ask whether to run alignment. - Research — optional reference for codebase details. Check context or
design-docs/NN-name.research.md.
Process
Phase 1 — Define the Tracer Bullet
- Read the alignment document's desired end state and adopted patterns.
- Identify the thinnest end-to-end slice that exercises the core path — from data layer through service logic to the outermost interface (API, UI, CLI, or whatever the system exposes).
- This is Phase 1 of the frame. It must cross all relevant layers. A phase touching only one layer is a horizontal slice — restructure it.
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.
- yesterday First seen · 194 lines · 46 tokens per session scan A 778fccb3090c
frame is a skill published in the GitHub repository xobotyi/cc-foundry (20 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 1,743 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…