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 infraspecdev/tesseract --skill plan-docsgit clone --depth 1 https://github.com/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/plan-docs)<a href="https://agentmods.dev/skills/infraspecdev/tesseract/plan-docs"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/plan-docs/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/infraspecdev/tesseract/plan-docs"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/plan-docs.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.00049 | $0.02286 |
| Opus 5.5 | $0.00020 | $0.00914 |
| Sonnet 5.5 | $0.00010 | $0.00457 |
| Haiku 4.5 | $0.00005 | $0.00229 |
Grade A, and why
plan-docs scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Vague acceptance criteria ("networking works") | Testable: "curl ifconfig.me returns 65.2.46.44" | How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Docs
Create two-document planning artifacts for infrastructure phases: an architecture/ADR doc and a detailed execution plan with stories that become project management cards.
Output Format
Default: HTML. User can request Markdown instead. Ask if not specified.
When to Use
- Creating a new infrastructure phase or project milestone
- Breaking down a large initiative into executable stories
- Writing an ADR with a paired execution plan
- User mentions "phase plan", "detailed plan", "architecture doc", "story breakdown"
Document Types
1. Architecture / ADR
The "why and how" — explains the problem, current state, proposed solution, and key decisions.
Structure:
- Nav bar — links to overview, detailed plan, adjacent phases
- Phase heading with timeline, month, dependencies
- Problem — 1-2 paragraphs on what's broken or missing
- Context — existing infrastructure table (Resource | Details | Status: Exists/To create), current state tables
- Solution — approach paragraph, ASCII diagram in
<pre>, "what changes" table, "what does NOT change" list - Key insights — in
<blockquote>blocks (always blue#1a73e8, never phase-colored) - Inter-service / integration impacts — how this affects other systems
- Deliverables — bullet list of concrete outputs
- Rollback strategy — how to undo if things go wrong
2. Detailed Execution Plan
The "what to do" — stories that become ClickUp cards via sprint-planner sync.
Structure:
- Nav bar — links to overview, architecture doc
- Phase heading with week range and one-line summary
- EPIC metadata block — ClickUp EPIC link (or
to createbadge), status, assignee, timeline - Infrastructure section — resource inventory table (Resource | ID/Value | Status)
- Stories summary table — index, linked story name, ClickUp badge, status badge, assignee
- Story sections — each story as a card-ready block (see Story Format below)
- Phase success criteria — overall acceptance criteria in
.success-criteriablock
What ships with it
1 file 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 First seen · 192 lines · 49 tokens per session scan A af8e703087c5
plan-docs is a skill published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 2,286 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…