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.
git 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/commands/infraspecdev/tesseract/pm-sync)<a href="https://agentmods.dev/commands/infraspecdev/tesseract/pm-sync"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/pm-sync/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/commands/infraspecdev/tesseract/pm-sync"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/pm-sync.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.00036 | $0.01366 |
| Opus 5.5 | $0.00014 | $0.00546 |
| Sonnet 5.5 | $0.00007 | $0.00273 |
| Haiku 4.5 | $0.00004 | $0.00137 |
Grade A, and why
pm-sync 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Sync
Sync plan document stories against your project management tool. Includes
forwarding of each story's design_refs[] as web links on the synced task
(idempotent upsert keyed by sha256(story_id + anchor_url)[:32]).
Usage
/pm-sync · /pm-sync --tool <clickup|jira|confluence|notion> (override adapter)
Paths
This command mutates {plan_json} = {output_dir}/{feature}/plan.json in place — adding PM tool IDs and URLs to stories after sync. It does NOT write any new files; the {plan_md} / {plan_html} renders are regenerated from the updated sidecar by the /plan rendering flow.
Behavior
- Check that a PM tool is configured (
~/.shield/projects/<project>/pm.json→adapter) - If not configured, suggest running
/shield initto set up PM integration - Invoke the
shield:pm-syncskill - The skill:
- Calls
pm_get_capabilitiesto verify adapter supports sync - Reads
{plan_json}={output_dir}/{feature}/plan.jsonfor story data - Calls
pm_syncto diff against PM state - Presents diff as table (match/new/updated/unlinked)
- Asks user: apply all / pick which / cancel
- For new stories: calls
pm_bulk_create- Stories are sent with
epic_label+index+ barename(display name formatted adapter-side);epic_idis the relationship link target only.
- Stories are sent with
- For updates: calls
pm_bulk_update - For each story with
design_refs[]: calls the adapter'sforward_design_refs(task_id, refs) -> ForwardResult. Anchorless placeholders (LLDTODO) are skipped without an HTTP write. - Updates
{plan_json}with PM IDs and URLs - Re-renders
{plan_md}/{plan_html}from the updated sidecar
- Calls
- Invoke
shield:summarizeto produce a sync summary - Offer next steps:
/pm-status,/implement
design_refs[] forwarding contract
Every adapter (ClickUp, Jira, Confluence, Notion) implements the same signature
from shield/adapters/_common/shield_adapters_common/design_refs.py:
def forward_design_refs(task_id: str, refs: list[DesignRef]) -> ForwardResult: ...
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 · 119 lines · 36 tokens per session scan A 7775bd3f6b5e
pm-sync is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 1,366 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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.