Borrowing it
Nothing to install: this file belongs to Seven128/project-tiny-context-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Seven128/project-tiny-context-harness/main/.codex/ty-context-managed/skills/design-resource/SKILL.mdgit clone --depth 1 https://github.com/Seven128/project-tiny-context-harnessWrote 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/seven128/project-tiny-context-harness/design-resource)<a href="https://agentmods.dev/skills/seven128/project-tiny-context-harness/design-resource"><img src="https://agentmods.dev/badge/skills/seven128/project-tiny-context-harness/design-resource/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.
<a href="https://agentmods.dev/skills/seven128/project-tiny-context-harness/design-resource"><img src="https://agentmods.dev/badge/skills/seven128/project-tiny-context-harness/design-resource.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.01030 |
| Opus 5.5 | $0.00017 | $0.00412 |
| Sonnet 5.5 | $0.00008 | $0.00206 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
design-resource 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 1mo 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design resources
Deliver resources that people and agents can inspect and continue editing. Use Stitch for visual generation and design revisions, following the user's design direction and project constraints. This capability selects the tool; project Context supplies design rules, style and business meaning. It adds no fixed target platform or task workflow.
Project extensions
This capability can be used directly or composed into an existing project resource Skill. Apply relevant project-declared target-platform, reference, export and integration methods alongside it; reuse an already loaded extension without creating a circular read. Keep Stitch as the generator and visual editor; a wrapper must not silently substitute another provider. A project Skill may reference this installed entry and then supply its own methods instead of copying the generic instructions. Resolve this entry's relative references from its own directory. This is instruction composition, not an automatic extension loader.
Project Context owns confirmed style, design principles, business and interaction rules, scope and decisions with reasons. Tool operations, design methods and repeatable procedures belong in the project's Skill. Keep exact tokens, component definitions and resource entities in their actual source files or design tools, with Context pointing to those owners. Project-specific constraints refine this general capability; handle a material conflict explicitly under the user's requirements rather than silently replacing either source.
Create or revise resources
Read the user input, default Context, affected owners, existing design rules and necessary implementation. Separate constraints to preserve, confirmed choices, requested changes and open exploration. Follow owners from the affected page, component or capability even when the request does not mention design resources. Existing project organization is sufficient; no new design document is a prerequisite.
Continue a selected direction. Choose the number of alternatives, iterations and covered pages or states from the task; a selection is not necessarily formal adoption. Do not manufacture another revision when none is requested.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 41 lines · 42 tokens per session scan A 47959048bc35
design-resource is a skill published in the GitHub repository Seven128/project-tiny-context-harness (4 stars, last pushed 11d ago), licensed MIT. It adds 42 tokens to every session and 1,030 once invoked, about $0.0002 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-09-08.
Other skills, from other repositories
frontend-ux-engineer
Use for frontend features, Next.js/React/Vue/Svelte UI, accessibility, responsive layout, design polish, state handling, forms, visual QA, or product workflow improvements.
design-method
Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.
design-webapp
Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.
design-web
Use when building or revising a marketing/landing/campaign page, register brand locked at Gate 0 — use design-webapp for app screens instead.
design-motion
Use when adding or reviewing motion on an already-settled layout or component — never to hide or compensate for an unfinished one.
design-review
Use when a design deliverable is about to be reported done — the final quality gate after design-motion or a mobile mockup.