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 pantheon-org/tekhne --skill load-contextgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/load-context)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/load-context"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/load-context/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/pantheon-org/tekhne/load-context"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/load-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 81 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Excessive Agency · line 88 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.01750 |
| Opus 5.5 | $0.00018 | $0.00700 |
| Sonnet 5.5 | $0.00009 | $0.00350 |
| Haiku 4.5 | $0.00005 | $0.00175 |
Grade A, and why
load-context 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 14d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load Context
Load session state from CONTEXT-{stream}-llm.md in the session directory and optionally expand full resources.
.context/session/
INDEX.md index of streams
CONTEXT-llm.md default stream
CONTEXT-{name}-llm.md named stream
done/CONTEXT-{name}-llm.md archived stream (status done or parked)
Speed: < 3 seconds (default), 5-8 seconds (--full)
⚠️ AskUserQuestion Guard
CRITICAL: After EVERY AskUserQuestion call, check if answers are empty/blank. Known harness bug: outside Plan Mode, AskUserQuestion can silently return empty answers without showing UI.
If answers are empty: DO NOT proceed with assumptions. Instead:
- Output: "Questions didn't display (known AskUserQuestion bug outside Plan Mode)."
- Present the options as a numbered text list and ask user to reply with their choice number.
- WAIT for user reply before continuing.
Performance Rules
- Use
rtkfor shell commands when it is installed (a harness hook may already rewrite them; bare commands are also fine) - Parallel tool calls — ALL independent calls in one message
- Minimize round-trips
- No unnecessary synthesis — present parsed data directly
Workflow
Phase 1: Detect & Read (parallel)
Bash: ls -t .context/session/CONTEXT-*llm.md .context/session/done/CONTEXT-*llm.md 2>/dev/null || true
Read: .context/session/CONTEXT-{stream}-llm.md (if stream known from $ARGUMENTS)
If not found in the session directory, check its done/ subfolder. If found there, note 📦 (from done/) in report.
If multiple streams and no selection → AskUserQuestion with options (mark done/ files with 📦).
Filename: default → CONTEXT-llm.md, {name} → CONTEXT-{name}-llm.md
Phase 2: Expand Resources (if --full)
Parallel Read: OpenSpec project/proposal/tasks.md, top 3 hot files, manifest.yaml. DO NOT restore tasks — informational only.
Thinking Artifacts (if ## Thinking Artifacts section exists in CONTEXT file):
- Default mode: display artifact paths in resume report (no content read)
--fullmode: Read referenced thinking artifacts and include brief summaries in report
What ships with it
30 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.
- .audits/2026-04-11/analysis.md 1.2 KB
- .audits/2026-04-11/audit.json 485 B
- .audits/2026-04-11/remediation-plan.md 3.6 KB
- .audits/2026-09-30/Analysis.md 482 B
- .audits/2026-09-30/audit.json 545 B
- .audits/2026-09-30/Remediation.md 1.8 KB
- .audits/latest 10 B
- .tekhne/plugin.json 231 B
- CHANGELOG.md 323 B
- evals/instructions.json 1.9 KB
- evals/scenario-1/capability.txt 84 B
- evals/scenario-1/criteria.json 1.8 KB
- evals/scenario-1/task.md 284 B
- evals/scenario-2/capability.txt 93 B
- evals/scenario-2/criteria.json 1.6 KB
- evals/scenario-2/task.md 200 B
- evals/scenario-3/capability.txt 71 B
- evals/scenario-3/criteria.json 1.6 KB
- evals/scenario-3/task.md 389 B
- evals/scenario-4/capability.txt 107 B
- evals/scenario-4/criteria.json 1.6 KB
- evals/scenario-4/task.md 232 B
- evals/scenario-5/capability.txt 76 B
- evals/scenario-5/criteria.json 1.6 KB
- evals/scenario-5/task.md 229 B
- evals/scenario-6/capability.txt 69 B
- evals/scenario-6/criteria.json 1.5 KB
- evals/scenario-6/task.md 122 B
- evals/summary.json 155 B
- references/reference.md 2.4 KB
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.
- 14d ago Changed · -1 lines b656fb98ea79
- 21d ago Changed · +31 lines c4c498809332
- 1mo ago First seen · 121 lines · 46 tokens per session scan A 3974c648f6c0
load-context is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,750 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-08-31.
Other skills, from other repositories
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
vite
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.