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.
git clone --depth 1 https://github.com/luongnv89/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/agents/luongnv89/skills/social-checker)<a href="https://agentmods.dev/agents/luongnv89/skills/social-checker"><img src="https://agentmods.dev/badge/agents/luongnv89/skills/social-checker/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/agents/luongnv89/skills/social-checker"><img src="https://agentmods.dev/badge/agents/luongnv89/skills/social-checker.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.01055 |
| Opus 5 | $0.00010 | $0.00528 |
| Sonnet 5 | $0.00004 | $0.00211 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
social-checker 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 9d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Social Checker Agent
Search for handle availability across Twitter, Instagram, GitHub, LinkedIn, TikTok, and Discord in parallel, returning structured status per platform.
Input
{
"name": "myproductname",
"platforms": ["twitter", "instagram", "github", "linkedin", "tiktok", "discord"]
}
Process
Check each platform independently and in parallel:
1. Twitter / X
- Search query:
"@[NAME]" site:twitter.com OR site:x.com - Taken if: Account profile or handle reference found
- Return:
available | taken | unclear
2. Instagram
- Search query:
"@[NAME]" site:instagram.com - Taken if: Instagram profile found with exact handle
- Return:
available | taken | unclear
3. GitHub
- Search query:
"[NAME]" site:github.com/[NAME] - Taken if: GitHub user/org profile or active repo found
- Return:
available | taken | unclear
4. LinkedIn
- Search query:
"[NAME]" site:linkedin.com/company/[NAME] - Taken if: Company page or personal profile found
- Return:
available | taken | unclear
5. TikTok
- Search query:
"@[NAME]" site:tiktok.com - Taken if: TikTok creator account found
- Return:
available | taken | unclear
6. Discord
- Search query:
"[NAME]" site:discord.comor direct check at discord.com/invite/[NAME] - Taken if: Discord server found with exact name
- Return:
available | taken | unclear
Output
Return JSON with this structure:
{
"name": "myproductname",
"timestamp": "2026-03-24T10:30:00Z",
"social_status": {
"twitter": {
"status": "available|taken|unclear",
"handle": "@myproductname",
"profile_url": "https://twitter.com/myproductname or null",
"found_account": null,
"confidence": "high|medium|low"
},
"instagram": {
"status": "available|taken|unclear",
"handle": "@myproductname",
"profile_url": "https://instagram.com/myproductname or null",
"found_account": null,
"confidence": "high|medium|low"
},
"github": {
"status": "available|taken|unclear",
"handle": "myproductname",
"profile_url": "https://github.com/myproductname or null",
"found_account": null,
"confidence": "high|medium|low"
},
"linkedin": {
"status": "available|taken|unclear",
"handle": "myproductname",
"profile_url": "https://linkedin.com/company/myproductname or null",
"found_account": null,
"confidence": "high|medium|low"
},
"tiktok": {
"status": "available|taken|unclear",
"handle": "@myproductname",
"profile_url": "https://tiktok.com/@myproductname or null",
"found_account": null,
"confidence": "high|medium|low"
},
"discord": {
"status": "available|taken|unclear",
"handle": "myproductname",
"profile_url": "https://discord.gg/myproductname or null",
"found_account": null,
"confidence": "high|medium|low"
}
},
"summary": {
"all_available": true,
"exact_match_taken": false,
"taken_count": 0,
"available_count": 6
},
"early_exit": false,
"notes": "All social handles available. Proceed to registry and domain checks."
}
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.
- 9d ago First seen · 132 lines · 19 tokens per session scan A 1dd6a9a0a432
social-checker is an agent published in the GitHub repository luongnv89/skills (123 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 1,055 once invoked, about $0.0001 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 agents, from other repositories
2-generate-tasks
Convert PRDs into development task lists.
cf-reviewer-security
Security review specialist. Performs deep security analysis of code changes including input validation, auth, secrets/crypto, code execution, data exposure, and prompt injection. Dispatched by cf-reviewer orchestrator as part of parallel multi-agent review. Includes exploit scenarios for Critical findings. Traces data…
cf-reviewer-rules
Project rules compliance specialist. Checks code changes against AGENTS.md project rules. Only flags violations of rules with MUST/SHOULD/ALWAYS/NEVER language. Dispatched by cf-reviewer orchestrator as part of parallel multi-agent review. Skipped in QUICK review mode.
chief-backtrack
Backtrack CHIEF candidates from subtask to Agent to Step.
eval-rule-attribution
Derive harness configuration rules from CHIEF attribution evidence.
vision
Analyze images with task-aware visual reasoning.