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 commands/ogrodev/fsociety/ty-githubgit clone --depth 1 https://github.com/ogrodev/fsocietyWrote 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/commands/ogrodev/fsociety/ty-github)<a href="https://agentmods.dev/commands/ogrodev/fsociety/ty-github"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/ty-github.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.00015 | $0.00970 |
| Opus 5 | $0.00008 | $0.00485 |
| Sonnet 5 | $0.00003 | $0.00194 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade C, and why
ty-github scanned grade C with 2 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 today.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/tyrell-scan-$$ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -H "Authorization: Bearer ${GITHUB_TOKEN}" \ How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are executing a GitHub/GitLab leak scan for the tyrell data exfiltration plugin.
Step 1 — Generate Search Queries
Run the hunt engine to produce optimized code repository search queries:
node "${CLAUDE_PLUGIN_ROOT}/scripts/hunt-engine.js" github $ARGUMENTS
The script returns query objects with fields: platform (github|gitlab), query, type, file_extensions, and rationale. Query types cover secrets, config files, database dumps, and environment files.
Step 2 — Execute GitHub Code Search
For each query targeting GitHub:
# Via GitHub CLI (preferred)
gh search code "<query>" --limit 50 --json repository,path,url,textMatches
# Via GitHub REST API (fallback)
curl -s -H "Authorization: Bearer ${GITHUB_TOKEN}" \
-H "Accept: application/vnd.github.v3+json" \
"https://api.github.com/search/code?q=<url-encoded-query>&per_page=50" | \
jq '.items[] | {repo: .repository.full_name, path: .path, url: .html_url}'
Step 3 — Execute GitLab Search
For each query targeting GitLab:
curl -s -H "PRIVATE-TOKEN: ${GITLAB_TOKEN}" \
"https://gitlab.com/api/v4/search?scope=blobs&search=<url-encoded-query>" | \
jq '.[] | {project: .project_id, filename: .filename, ref: .ref, startline: .startline}'
Step 4 — Deep-Scan Identified Files
For each promising file returned by search results, fetch and analyze its content:
# Fetch raw file content from GitHub
curl -s -H "Authorization: Bearer ${GITHUB_TOKEN}" \
"https://raw.githubusercontent.com/<owner>/<repo>/<branch>/<path>"
# Clone and scan with gitleaks (if repo is public)
git clone --depth=1 "https://github.com/<owner>/<repo>" /tmp/tyrell-scan-$$
gitleaks detect --source=/tmp/tyrell-scan-$$ --report-format=json --report-path=/tmp/gitleaks-$$.json
cat /tmp/gitleaks-$$.json | jq '.[] | {rule: .RuleID, file: .File, secret: .Secret, commit: .Commit}'
rm -rf /tmp/tyrell-scan-$$
For secrets detection with trufflehog:
trufflehog github --repo="https://github.com/<owner>/<repo>" --json 2>/dev/null | \
jq '{detector: .DetectorName, verified: .Verified, raw: .Raw, file: .SourceMetadata.Data.Github.file}'
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.
- today First seen · 106 lines · 15 tokens per session scan C 7029d78e63a3
ty-github is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 970 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
better-auth:setup
Interactive setup wizard for better-auth authentication. Guides through database, framework, OAuth providers, and plugin configuration.
v-memory-refresh
(Re)index docs/superpowers prose into the local V-memory cache so recall is current. Incremental by file hash; runs fully offline (FTS5, pure stdlib). Optionally enable the semantic lane with a one-time bootstrap. Run it after pulling new docs, or when /v:remember looks stale.
symfony-migrations
Create and manage Doctrine migrations for database schema changes.
pentest
Activate pentest mode — displays ASCII art, configures session isolation, collects engagement scope, then OWNS the engagement: pre-flight, recon, planning (via the pentester-orchestrator planner), executor dispatch, a time-budget quota loop, aggregation, and report generation.
pentest-attacks
Define the attack profile for an engagement — select which attack categories and skills to use. Saves to .pentest-attacks.json. If run before /pentest:pentest, the orchestrator will respect the selection. If run standalone, does not launch a pentest.
pentest-scope
Define or update engagement scope — saves scope to disk without launching a pentest. Can be run before or during an engagement. If a pentest is active and the target changes drastically, warns the operator and suggests a new engagement.