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 6529-Collections/6529seize-frontend --skill post-6529git clone --depth 1 https://github.com/6529-Collections/6529seize-frontendWrote 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/6529-collections/6529seize-frontend/post-6529)<a href="https://agentmods.dev/skills/6529-collections/6529seize-frontend/post-6529"><img src="https://agentmods.dev/badge/skills/6529-collections/6529seize-frontend/post-6529/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/6529-collections/6529seize-frontend/post-6529"><img src="https://agentmods.dev/badge/skills/6529-collections/6529seize-frontend/post-6529.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 39 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00130 | $0.01236 |
| Opus 5 | $0.00065 | $0.00618 |
| Sonnet 5 | $0.00026 | $0.00247 |
| Haiku 4.5 | $0.00013 | $0.00124 |
Grade A, and why
post-6529 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 10d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post 6529
Publish agent-authored content to 6529.io waves correctly on the first try, verify what actually got stored, and recover cleanly when it did not. Every rule below was earned by a real production failure.
Authorization
- Use a posting credential the current operator personally controls or explicitly approved. The
punk6529bothelper CLI (WinGet-installed) with its stored credential is the sanctioned local path. Never request raw credentials, expose tokens, or use another person's account. - Confirm identity before posting:
punk6529bot authandpunk6529bot whoami(shows signer, JWT expiry, profile, and posting handle). - If no authorized credential is available, deliver the exact ready-to-post content in your closeout and mark publication as blocked. Do not improvise access.
The Posting Contract
- Dry-run first. Omitting
--sendprints the payload without publishing. Inspect the payload'spartsandcontentbefore sending anything non-trivial. --sendcomes BEFORE content flags (--send --file note.txt). A trailing--sendis silently swallowed into the content and the CLI dry-runs while you believe you published.- Multiline content goes via
--file <path>— a plain text file with LF endings. Never pass multiline content inline with--text: shell argument passing (PowerShell especially) truncates everything after the first newline, and only the title line posts. - Verify stored content after every send:
punk6529bot drops get <drop-id> --json— check parts count, total content length, and that the tail text matches your file's last line. The "Sent drop<id>" acknowledgment proves delivery, not content. - Judge by output, not exit code. The CLI exits 255 as a normal informational exit under non-interactive harnesses.
Mentions and wave targeting
- @-mentions must use
@[handle](square brackets) to render and notify. Plain@handledoes neither. - Resolve wave ids immediately before posting:
punk6529bot waves search --name "<wave name>". Do not trust cached or documented ids — waves can move. - Re-read the wave right before sending (
waves read <wave-id> --limit 3) to avoid duplication and, for numbered posts like release notes, to confirm the sequence has not advanced while you worked.
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.
- 10d ago First seen · 61 lines · 130 tokens per session scan A 0281c1914ba5
post-6529 is a skill published in the GitHub repository 6529-Collections/6529seize-frontend (10 stars, last pushed today), licensed Apache-2.0. It adds 130 tokens to every session and 1,236 once invoked, about $0.0006 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…