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/skills/authoring/harness_package_design/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/harness_package_design)<a href="https://agentmods.dev/skills/seven128/project-tiny-context-harness/harness_package_design"><img src="https://agentmods.dev/badge/skills/seven128/project-tiny-context-harness/harness_package_design/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/harness_package_design"><img src="https://agentmods.dev/badge/skills/seven128/project-tiny-context-harness/harness_package_design.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.00023 | $0.00197 |
| Opus 5.5 | $0.00009 | $0.00079 |
| Sonnet 5.5 | $0.00005 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
harness_package_design 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.
What it actually says
Package maintenance
Tiny Context preserves durable project facts and one short development contract. Read relevant Context and preserve user-authorized scope. Existing user requirements and security constraints survive tool retirement.
Edit the actual canonical owner, then synchronize package and installed generated copies through source-mappings.yaml. Keep public guidance English-complete and repository-only authoring instructions out of consumer assets.
Protect user files and mixed configuration. Explicit upgrades own semantic migration; sync only refreshes supported managed assets. Preserve path safety, concurrent-change detection and recoverability. Never equate a multi-file replacement with filesystem atomicity.
Run affected checks while working, then current-candidate regression, source parity/idempotence and actual tarball consumer checks for distribution changes. Report what was checked and material limitations. Do not preserve retired machine proof, role workflow or ROI governance as a requirement for maintenance.
What ships with it
5 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 Changed · -36 lines · -17 tokens per session 5a081c5ba006
- 2mo ago First seen · 51 lines · 40 tokens per session scan A 87d52eed7627
harness_package_design is a skill published in the GitHub repository Seven128/project-tiny-context-harness (4 stars, last pushed 11d ago), licensed MIT. It adds 23 tokens to every session and 197 once invoked, about $0.0001 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-31.
Other skills, from other repositories
agentic-code-review
Use when reviewing a diff, pull request, branch, or AI-generated code for correctness, security, regression, test, performance, and maintainability risks before merge.
hooksmith
Use when designing or reviewing safe Grok Build hooks for linting, tests, formatting, notifications, command guards, lifecycle automation, or project hook trust decisions.
repo-health-check
Use when auditing a repo before changes to find the smallest safe PR, quality risks, stale docs, missing tests, ignored-file gaps, or agent setup issues. Best first skill for unfamiliar codebases.
architecture-review
Use for clean architecture, modular monoliths, hexagonal boundaries, service boundaries, data flow, dependency direction, ADRs, or large feature planning.
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.
git-github-flow
Use for branch prep, clean commits, PR descriptions, GitHub issue triage, changelogs, release notes, review response, merge readiness, or publishing a branch safely.