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 tomzx/agents --skill sync-articlesgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/sync-articles)<a href="https://agentmods.dev/skills/tomzx/agents/sync-articles"><img src="https://agentmods.dev/badge/skills/tomzx/agents/sync-articles/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/tomzx/agents/sync-articles"><img src="https://agentmods.dev/badge/skills/tomzx/agents/sync-articles.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 Rogue Agent · line 80 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00091 | $0.02448 |
| Opus 5 | $0.00046 | $0.01224 |
| Sonnet 5 | $0.00018 | $0.00490 |
| Haiku 4.5 | $0.00009 | $0.00245 |
Grade A, and why
sync-articles 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 7d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TODAY=!date +%Y-%m-%d
Sync Articles
Runs a conformance pass over a set of articles in a blog content repository (one directory per slug, each with an index.md).
Each article is revised in place by its own opencode run job invoking the create-article skill, so every article gets a fresh context and the batch scales without one session accumulating the whole corpus.
After the jobs finish, the orchestrator verifies links, front matter, style rules, and AI disclosure tags across the diff, and reports a per-article summary.
This is the batch counterpart of create-article, which owns all per-article editing judgment.
For a single article, invoke /create-article directly.
For a report without edits, use /review-article.
Prerequisites
- Working directory is the root of the blog content repository (articles as
<slug>/index.mdwith YAML front matter, conventions in itsAGENTS.md). opencodeavailable on PATH, with thecreate-articleskill installed.rg,git, andpython3(withyaml) available on PATH.- The runner script next to this skill:
skills/sync-articles/sync-articles.
Scope and Modes
Resolve the article set from the arguments:
| Mode | Argument | Selection |
|---|---|---|
| Year (default) | --year <yyyy> |
created: in the given year, defaulting to the current year |
| Since | --since <yyyy-mm-dd> |
created: on or after the date |
| All | --all |
every article |
| Path filter | --path <glob> |
restrict any of the above to paths matching the glob |
Notes on create-article upstream guidance: it recommends running research-article first when sources are not yet gathered.
Skip that recommendation for this skill and say so when reporting: the articles already exist with their sources inline, and the task is conformance revision, not new research.
Workflow
Resolve scope -> build article list (rg over front matter)
|
v
Launch runner detached (one opencode run job per article, bounded concurrency)
|
v
Poll results file until all jobs finish
|
v
Verify: internal links, front matter, style rules, disclosure tags
|
v
Report per-article summary (changed files, fixes, failures)
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.
- 7d ago First seen · 222 lines · 91 tokens per session scan A 54931ee426de
sync-articles is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed 2d ago), licensed MIT. It adds 91 tokens to every session and 2,448 once invoked, about $0.0005 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-09-03.
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…