Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/akseolabs-seo/AK-Threads-boosternpx agentmods add skills/akseolabs-seo/ak-threads-booster/updateWrote 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/akseolabs-seo/ak-threads-booster/update)<a href="https://agentmods.dev/skills/akseolabs-seo/ak-threads-booster/update"><img src="https://agentmods.dev/badge/skills/akseolabs-seo/ak-threads-booster/update/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/akseolabs-seo/ak-threads-booster/update"><img src="https://agentmods.dev/badge/skills/akseolabs-seo/ak-threads-booster/update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Rogue Agent · line 3 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00069 | $0.01041 |
| Opus 5 | $0.00034 | $0.00521 |
| Sonnet 5 | $0.00014 | $0.00208 |
| Haiku 4.5 | $0.00007 | $0.00104 |
Grade A, and why
update 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AK-Threads-Booster Update Module
Use this module when the user wants to check whether AK-Threads-Booster has a newer version, update the local skill repo, or install an opt-in weekly update checker.
Repository:
https://github.com/akseolabs-seo/AK-Threads-booster
Safety Rules
- Never reset, rebase, stash, checkout over, or discard local files automatically.
- Never overwrite a dirty working tree.
- Only apply updates when the repo is clean and the upstream update can fast-forward.
- If local-only commits, untracked files, uncommitted edits, or conflicts exist, stop and report the blocker.
- Updating the skill code is separate from
/refresh, which updates Threads tracker data.
User Intents
| Intent | Action |
|---|---|
| Check once / 有沒有新版 | Run one-time check, no apply unless user asks |
| Update now / 更新到最新版 | Run safe updater with --apply --validate |
| Install weekly auto-update / 每週自動檢查更新 | Create a Codex cron automation, only after explicit user request |
| Remove weekly auto-update / 取消自動更新 | Find and delete the matching automation |
Proactive Auto-Update Offer
After any successful one-time update check or update attempt, ask the user once:
要不要順手開啟每週自動檢查 AK-Threads-Booster 更新？
開啟後，每週會自動檢查 GitHub。有新版且本地 repo 乾淨時才會 fast-forward 更新；如果有本地修改、衝突或 local commits，會停下回報，不會覆蓋你的東西。
If the user says yes, install the weekly automation. If the user says no, do not ask again in the same run. Do not install by default.
When the user is in a non-interactive/headless context, do not install automation. Report that auto-update is available and requires explicit opt-in.
One-Time Check
Run from the repository root:
python scripts/check_skill_update.py --remote origin --branch main
Interpret:
up_to_date: no update.update_available: upstream has commits; ask whether to apply.blocked_*: do not apply; report blockers and recommended next step.
Update Now
Run:
python scripts/check_skill_update.py --remote origin --branch main --apply --validate
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 · 113 lines · 69 tokens per session scan A 35b74ad03b5f
update is a skill published in the GitHub repository akseolabs-seo/AK-Threads-booster (271 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 1,041 once invoked, about $0.0003 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-30.
Other skills, from other repositories
gr-social-distill
A content-repurposing workflow that turns one published blog post into several social-media formats, including an X thread, a Xiaohongshu post, a LinkedIn carousel, and a dev.to or Zenn article.
content-pillar-atomizer
Take 1 blog post or article and generate 15-30 platform-native micro-content pieces. Not reformatting — re-contextualizing for each platform's culture. Triggers on: "atomize this content", "repurpose my blog post", "turn this into social posts", "content atomizer", "pillar content", "one to many content", "repurpose…
twitter-thread-writer
Write X/Twitter threads that get bookmarked, shared, and drive affiliate clicks. Use this skill when the user asks about writing Twitter threads, X threads, tweet threads for affiliate marketing, or says "write a thread about X", "Twitter thread promoting X", "X thread for affiliate", "write tweets that go viral"…
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
dev
One-command dev loop boot. Spins up portless (named HTTPS subdomain), emulate (stateful API mocks), the project's dev server, and an agent-browser session, all keyed to the current git branch. Use when starting a feature branch, switching worktrees, or returning to a project after a break. Skips silently with install…
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.