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/seven128/project-tiny-context-harness/context_full_project_exportnpx skills add Seven128/project-tiny-context-harness --skill context_full_project_exportgit 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/context_full_project_export)<a href="https://agentmods.dev/skills/seven128/project-tiny-context-harness/context_full_project_export"><img src="https://agentmods.dev/badge/skills/seven128/project-tiny-context-harness/context_full_project_export.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 | $0.00104 | $0.01463 |
| Opus 5 | $0.00052 | $0.00732 |
| Sonnet 5 | $0.00021 | $0.00293 |
| Haiku 4.5 | $0.00010 | $0.00146 |
Grade A, and why
context_full_project_export 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 4d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Full Project Export
Package-Managed Boundary
This Skill is generated by ty-context sync and owned by the Harness package. Do not edit the generated context_full_project_export Skill directly.
This Skill creates a temporary export artifact only. It does not author durable Context and does not change project_context/context.toml.
Purpose
When the user needs a full project context export, project overall context export or external LLM handoff, create temporary export artifacts that collect project Context, key agent guidance, architecture/module facts, code navigation and bounded source support for copying into an external tool or one-off discussion.
When the user needs a code-level implementation export, create one temporary Markdown snapshot of current source and engineering configuration files for upload to Web GPT or another external model.
Workflow
- Prefer the bounded Source Pack for external LLM / Web GPT planning. It writes at most 5 files total under
tmp/ty-context/context-exports/latest/and removes old timestamped export rounds:npx --yes --package project-tiny-context-harness@latest ty-context export-context --source-pack
- Use
--code-indexwhen implementation navigation is enough and full source bodies are not needed:npx --yes --package project-tiny-context-harness@latest ty-context export-context --code-index
- Use
--task-context <name>for focused handoff, preferably with a profile or explicit include selectors:npx --yes --package project-tiny-context-harness@latest ty-context export-context --task-context <name> --profile <profile-id>npx --yes --package project-tiny-context-harness@latest ty-context export-context --task-context <name> --include-context project_context/areas/main.md --include-code 'src/example/**'
- Use legacy
--allwhen the user explicitly wants both old temporary artifacts in one command. Do not hand-write tracked export documents:npx --yes --package project-tiny-context-harness@latest ty-context export-context --all
- Use legacy
--fullwhen only the project Context bundle is needed:npx --yes --package project-tiny-context-harness@latest ty-context export-context --full
- Use legacy
--codewhen only the full code-level implementation snapshot is needed. It generates one Markdown file by default and is the full fallback when Source Pack bundles are not enough:npx --yes --package project-tiny-context-harness@latest ty-context export-context --code
- Custom output paths are allowed only for legacy single-artifact modes and must stay under the temporary export directory.
--alland Source Pack modes do not accept--output:npx --yes --package project-tiny-context-harness@latest ty-context export-context --full --output tmp/ty-context/context-exports/my-export.mdnpx --yes --package project-tiny-context-harness@latest ty-context export-context --code --output tmp/ty-context/context-exports/my-code-export.md
- Use dry-run mode to inspect planned sources before writing:
npx --yes --package project-tiny-context-harness@latest ty-context export-context --source-pack --checknpx --yes --package project-tiny-context-harness@latest ty-context export-context --code-index --checknpx --yes --package project-tiny-context-harness@latest ty-context export-context --task-context <name> --checknpx --yes --package project-tiny-context-harness@latest ty-context export-context --all --checknpx --yes --package project-tiny-context-harness@latest ty-context export-context --full --checknpx --yes --package project-tiny-context-harness@latest ty-context export-context --code --check
- After exporting, report artifact paths, source counts, recommended upload sets and warnings to the user. Do not summarize export contents back into Context.
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.
- 4d ago First seen · 71 lines · 104 tokens per session scan A dc4af5730e54
context_full_project_export is a skill published in the GitHub repository Seven128/project-tiny-context-harness (3 stars, last pushed 4d ago), licensed MIT. It adds 104 tokens to every session and 1,463 once invoked, about $0.0005 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
context-diet
Measure and compact an oversized agent-context file (CLAUDE.md, .cursorrules, AGENTS.md, a system prompt) without losing rules, or safely run reversible bounded, reversible ablation when intentional/aggressive context removal is requested. Triggers: "CLAUDE.md too big", "over the char limit", "context file too large"…
atlas-setup
Use when a repository needs Atlas setup, repair/update, AGENTS.md refresh, AI memory refresh, vocabulary cleanup, or review after major codebase changes.
continual-learning
Orchestrate continual learning by delegating transcript mining to agents-memory-updater and writing durable memory to local JSON (never root AGENTS.md Learned sections). USE WHEN continual learning, mine prior chats, maintain agent memory, or the stop hook triggers this skill.
deep-init
Generate an agent-agnostic, two-tier context layer for a codebase — a lean, always-loaded CLAUDE.md plus a deep, on-demand .ai/docs/ layer (business rules, live DB schema + ORM drift, cross-component workflows, and the WHY: ADRs + a knowledge log), every claim grounded to file:line and verified to exist. Built for…
atlas-compact
Use when AI context needs cleanup — atlas doctor context-size advisories, an oversized AGENTS.md or CLAUDE.md, bloated memory or vocabulary files, or durable docs that need compaction, relocation, or dedup.
maintain-project-ai-records
Initialize and maintain lightweight AI work records in a writable project. Use on the first substantive writable task and after meaningful milestones. Do not create records for read-only inspection or trivial answers.