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 blueberrycongee/termcanvas --skill using-termcanvasgit clone --depth 1 https://github.com/blueberrycongee/termcanvasWrote 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/blueberrycongee/termcanvas/using-termcanvas)<a href="https://agentmods.dev/skills/blueberrycongee/termcanvas/using-termcanvas"><img src="https://agentmods.dev/badge/skills/blueberrycongee/termcanvas/using-termcanvas/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/blueberrycongee/termcanvas/using-termcanvas"><img src="https://agentmods.dev/badge/skills/blueberrycongee/termcanvas/using-termcanvas.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.00029 | $0.00751 |
| Opus 5.5 | $0.00012 | $0.00300 |
| Sonnet 5.5 | $0.00006 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
using-termcanvas 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using TermCanvas
Route first. Choose the lightest path that preserves correctness.
Routing
- If the user wants to challenge, stress-test, or critically review an idea, argument, or proposal, use
challenge. - If the user asks to investigate a bug, debug, or diagnose an issue, use
investigate. - If the user asks for a security review or audit, use
security-audit. - If the user asks for a code review or diff review, use
code-review. - If the user asks to test a site, QA a page, or verify a deploy, use
qa. - If the task is simple, local, high-certainty, or faster in the current agent, do it directly. Do not invoke Hydra by default.
- If the task needs an isolated worktree, file evidence, retry/status control,
or a staged workflow, use
hydra. - Before using Hydra in a repo, ensure the project has current Hydra
instructions via
hydra init-repoor the TermCanvas Hydra enable action.
Hydra workflow patterns
Lead-driven, decision-point oriented. The Lead reads the codebase, picks
the strategy, and dispatches workers for the steps that need a fresh
agent process. Roles available: lead (the decider — not itself dispatched),
dev (writes code AND its tests), reviewer (independent cross-model
check). No separate researcher — the Lead does its own research. No
separate tester — dev owns its own test surface.
hydra init --intent "..." --repo .then dispatchdev->reviewerfor ambiguous, risky, or PRD-driven work- call
hydra watchafter each dispatch to wait for the decision point
- call
hydra spawn --task "..." --repo .for a single isolated worker- use when the task split is already known and you do not need the full Lead-driven loop
Hydra worker primitive
hydra spawn --task "..." --repo .- one direct isolated worker terminal
- use when the task split is already known and you do not need a full workflow
Guardrails
- Do not describe Hydra workflows as automatic parallelism unless multiple spawned workers are actually involved.
- When launching Claude/Codex tasks via TermCanvas CLI, use
termcanvas terminal create --prompt "..."rather thantermcanvas terminal input. - After
hydra dispatch, immediately starthydra watch— do not ask whether to watch. - Use
hydra watch/hydra status/hydra ledger/hydra list --workflowsfor workflows created byhydra init. - Use
hydra listandhydra cleanup <agentId>for direct workers created byhydra spawn. - Prefer structured Hydra state and files over terminal prose.
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 · 67 lines · 29 tokens per session scan A e6db081db7e6
using-termcanvas is a skill published in the GitHub repository blueberrycongee/termcanvas (413 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 751 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-30.
Other skills, from other repositories
ai-evaluation-patterns
Guides expert-level ai evaluation patterns implementation: ai-ml and testing decision frameworks, production-ready patterns, and concrete templates for ai evaluation patterns workflows. Use when the user asks about ai evaluation patterns, ai evaluation patterns configuration, or ai-ml best practices for ai projects.…
automation-architect
Workflow automation design using Zapier, Make, and n8n covering trigger-action architecture, multi-step automation workflows, error handling strategies, personal versus business automation patterns, ROI calculation, and a library of common automation recipes. Use when the user asks about automation architect, related…
sales-icp
Build a comprehensive Ideal Customer Profile (ICP) for any B2B business - firmographic, technographic, behavioral, pain-point, budget, and channel dimensions, plus negative ICP, 100-point scoring rubric, buyer personas, prospecting playbook, and a draft first-outreach message that inherits sales-outreach Phase 0…
sales-qualify
Qualify a sales lead using BANT (Budget/Authority/Need/Timeline) and MEDDIC (Metrics/Economic Buyer/Decision Criteria/Decision Process/Identify Pain/Champion) frameworks against publicly available signals using OSINT only - no scraping of platforms whose ToS forbid it (LinkedIn §8.2, Glassdoor, G2, Capterra…
content-haro-reply
Write a HARO (Help A Reporter Out) or Qwoted/SourceBottle expert-source reply that gets quoted - not buried. Opens with a credentialed one-liner that answers "why this person, for this query," delivers the answer in 3-5 tight bullets with specifics and a contrarian take, and closes with a pull quote written to be…
convert-package
Build a complete sales asset end-to-end via The Donahoe Method: diagnostic → primitives → fingerprint → page → integrity-gate → visual → audit → report. Composite orchestrator that calls 14-16 sub-skills via delegatetask in an 8-phase DAG (sequential where dependencies require it, parallel where they don't). Produces…