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 patrick-toulme/harnessgym --skill tensor-plan-optimizergit clone --depth 1 https://github.com/patrick-toulme/harnessgymWrote 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/patrick-toulme/harnessgym/tensor-plan-optimizer)<a href="https://agentmods.dev/skills/patrick-toulme/harnessgym/tensor-plan-optimizer"><img src="https://agentmods.dev/badge/skills/patrick-toulme/harnessgym/tensor-plan-optimizer.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.00072 | $0.01672 |
| Opus 5 | $0.00036 | $0.00836 |
| Sonnet 5 | $0.00014 | $0.00334 |
| Haiku 4.5 | $0.00007 | $0.00167 |
Grade A, and why
tensor-plan-optimizer 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 7d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tensor Plan Optimizer
Use the MCP suite first:
- Manifest:
.harnessgym/mcp/tensor-plan-server/harnessgym-mcp.json - Server:
.harnessgym/mcp/tensor-plan-server/tensor_plan_server.py - Smoke test:
python3 .harnessgym/mcp/tensor-plan-server/tensor_plan_server.py --self-test - Codex exec helper:
python3 .harnessgym/runtime/mcp_call.py --server tensor-plan-server --tool run_objective --arguments '{"mode":"dev"}'
For Codex exec, use the workspace-local helper above if native MCP tools are not visible. Do not write a one-off JSON-RPC client or launch the server directly; the helper calls through HarnessGym telemetry so the run records real generated-tool usage in .harnessgym/mcp_calls.jsonl.
Workflow
- Call
run_objectiveindevmode to confirm the current score. - Call
trace_summaryon the current plan to identify bank conflicts, DMA penalties, spill pressure, scratchpad pressure, and synergies. - Call
resume_search_historyto find the best fixtures/history seeds before repeating any sweep. - Call
local_neighborhood_searchwithstrategy=checkpointaround the current best fixture or plan. This covers single, pair, and bounded grid mutations and is the fastest way to reproduce the iteration-2 local-search win. - Call
bounded_exhaustive_searchwithprofile="iteration3_dev_core"and, if time permits,profile="iteration3_layout_relaxed". These profiles encode the manual iteration-3 sweeps that found no better dev plan than the iteration-2 fixture while checking dev winners against final mode. - Call
search_planswithstrategy=quickfor broader randomized exploration. Usestrategy=focusedonly when there is time for a broader deterministic sweep around the best discovered region. - Call
candidate_diffandbenchmark_planwithmodes=["dev","final"]for promising candidates.devis the fast objective;finalis the authoritative held-out comparison. - Call
apply_best_verifiedorapply_candidatewithdry_run=truefirst. Only usedry_run=falseafter the candidate improvesdev, passesfinal, and preserves correctness. - Call
export_candidate_fixturefor a verified improvement that should seed the next attempt. - Call
compare_historybefore final reporting so the best explored candidate is not lost.
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.
- 7d ago First seen · 94 lines · 72 tokens per session scan A 1be220e29d9b
tensor-plan-optimizer is a skill published in the GitHub repository patrick-toulme/harnessgym (41 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,672 once invoked, about $0.0004 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-30.
Other skills, from other repositories
dataset-evaluation
Validates dataset formatting and quality for SageMaker model fine-tuning (SFT, DPO, or RLVR). Use when the user says "is my dataset okay", "evaluate my data", "check my training data", "I have my own data", or before starting any fine-tuning job. Detects file format, checks schema compliance against the selected model…
llm-evaluation
LLM evaluation and testing patterns including prompt testing, hallucination detection, benchmark creation, and quality metrics. Use when testing LLM applications, validating prompt quality, implementing systematic evaluation, or measuring LLM performance.
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
dbt-transformation-patterns
Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or implementing analytics engineering best practices.
nemo-automodel-model-onboarding
Guide for onboarding new model architectures into NeMo AutoModel, including architecture discovery, implementation patterns, registration, and validation.
nemo-automodel-recipe-development
Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.