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 mappedsky/seizu --skill pin-reportsgit clone --depth 1 https://github.com/mappedsky/seizuWrote 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/mappedsky/seizu/pin-reports)<a href="https://agentmods.dev/skills/mappedsky/seizu/pin-reports"><img src="https://agentmods.dev/badge/skills/mappedsky/seizu/pin-reports/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/mappedsky/seizu/pin-reports"><img src="https://agentmods.dev/badge/skills/mappedsky/seizu/pin-reports.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.00019 | $0.00407 |
| Opus 5.5 | $0.00008 | $0.00163 |
| Sonnet 5.5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
pin-reports 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.
What it actually says
Pin or unpin a Seizu report for the request the request input carries.
Inputs — the values arrive in the ## Inputs block below these instructions:
request— the pinning change to make.target_report_id— the report to pin or unpin.pinned— the pinned state to set.dry_run— when true, produce payloads without writing anything.
Tool arguments - use exactly these field names and no others:
- reports__list: no arguments
- reports__get: report_id
- reports__pin: report_id, pinned
Workflow:
- If
target_report_idis empty, callreports__listand identify the target report from the request. If more than one report matches, ask for the exact report. - Call
reports__getand confirm the report name, latest version, access scope, and current pinned state if visible from report metadata/list output. - Interpret
pinned=trueas pin andpinned=falseas unpin. Do not change report content. - If
dry_run=true, stop before callingreports__pinand show the exact payload. - If
dry_run=false, callreports__pinwithreport_idandpinned, then callreports__listorreports__getagain to verify the state.
Output format:
Target: report_id, name, access scope, latest version.Action: pin or unpin.Applied Changes: tool call result, or the dry-run payload.Verification: evidence that the report is now pinned or unpinned.
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 · 32 lines · 19 tokens per session scan A 8a74d593b130
pin-reports is a skill published in the GitHub repository mappedsky/seizu (5 stars, last pushed 16d ago), licensed Apache-2.0. It adds 19 tokens to every session and 407 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-11.
Other skills, from other repositories
gsd-tools
Central utility skill for GSD operations. Provides config parsing, slug generation, timestamps, path operations, and orchestrates calls to other specialized skills. Acts as the unified entry point that the original gsd-tools.cjs provided via its lib/ modules (commands, config, core, init).
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
spec-driven-development
Specification creation and management for the Pilot Shell methodology. Covers semantic search, clarifying questions, structured spec generation, and iterative refinement.
cog-meeting-processing
Process meeting recordings and transcripts into decisions, action items, and team dynamics.
cog-onboarding
Personalize COG Second Brain workflow through role pack selection and vault initialization.
cog-team-intelligence
Cross-reference GitHub, Linear, Slack, and PostHog with bidirectional sync for team briefs.