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 agentmods add instructions/sergebulaev/threads-skills/agents-mdgit clone --depth 1 https://github.com/sergebulaev/threads-skillsWrote 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/instructions/sergebulaev/threads-skills/agents-md)<a href="https://agentmods.dev/instructions/sergebulaev/threads-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/sergebulaev/threads-skills/agents-md.svg" alt="Measured on agentmods" 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 | $0.01496 | $0.01496 |
| Opus 5 | $0.00748 | $0.00748 |
| Sonnet 5 | $0.00299 | $0.00299 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade A, and why
threads-skills AGENTS.md 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 4d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project conventions - threads-skills
This file is for any Codex agent working on this repository. Read it before making changes. Conventions here are mandatory unless the user asks otherwise.
Versioning
- Single source of truth:
.codex-plugin/plugin.json,.agents/plugins/marketplace.json,.claude-plugin/plugin.json, and.claude-plugin/marketplace.json. Plugin manifests must always match on package name and version; marketplace entries must point to the same package; author, license, homepage, and the public skill-bundle description must stay aligned. - Keep
AGENTS.mdandCLAUDE.mdaligned when changing shared project rules. Codex-specific workflow details belong here; Claude-specific details belong inCLAUDE.md. - Codex marketplace install uses
.codex-marketplace/threads-skills/. Do not edit that generated package by hand. Update the root files first, then runpython3 scripts/sync_codex_marketplace.py. - Default: bump the PATCH segment (3rd level,
0.0.X). This is the automatic behavior for every shippable commit, regardless of how large the diff feels. Skill renames, lib API breaks, new features: still PATCH by default. - Only bump MINOR or MAJOR when the user explicitly asks for a higher rank ("this is minor", "make it 2.0", "bump major"). Do not promote on your own initiative even if semver textbook says so.
- After bumping, two steps are required:
- Tag the commit:
git tag -a v<X.Y.Z> -m "..."+git push origin v<X.Y.Z> - Publish a GitHub Release for the tag:
gh release create v<X.Y.Z> --title "v<X.Y.Z>" --notes "<changelog>" --latestA tag alone does NOT update the README release badge. The shields.io badge reads from the Releases API, not from raw tags. Skipping step 2 leaves it stale.
- Tag the commit:
Commits
- Primary author must be Sergey: every
git commitneeds--author="Sergey Bulaev <[email protected]>". Verify withgit log -1 --format='%an <%ae>'before pushing. - Co-author trailers are fine when appropriate.
- Verify locally before push: build never breaks, no broken refs in
SKILL.md, library smoke import passes.
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.
- 4d ago First seen · 117 lines · 1,496 tokens per session scan A 898d618025dd
threads-skills AGENTS.md is an instructions file published in the GitHub repository sergebulaev/threads-skills (20 stars, last pushed today), licensed MIT. It adds 1,496 tokens to every session, about $0.0075 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 instructions, from other repositories
x-skills AGENTS.md
AGENTS.md instructions for sergebulaev/x-skills, covering project conventions - x-skills, versioning, commits, skill bundle invariants and voice rules + reference layout.
x-skills CLAUDE.md
Claude Code instructions for sergebulaev/x-skills, covering project conventions - x-skills, versioning, commits, skill bundle invariants and voice rules + reference layout.
facebook-skills AGENTS.md
AGENTS.md instructions for sergebulaev/facebook-skills, covering project conventions - facebook-skills, versioning, commits, skill bundle invariants and voice rules + reference layout.
facebook-skills CLAUDE.md
Claude Code instructions for sergebulaev/facebook-skills, covering project conventions - facebook-skills, versioning, commits, skill bundle invariants and voice rules + reference layout.
tiktok-skills AGENTS.md
AGENTS.md instructions for sergebulaev/tiktok-skills, covering project conventions - tiktok-skills, versioning, commits, skill bundle invariants and voice rules + reference layout.
youtube-skills AGENTS.md
AGENTS.md instructions for sergebulaev/youtube-skills, covering project conventions - youtube-skills, versioning, commits, skill bundle invariants and voice rules + reference layout.