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/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/plugins/ogrodev/fsociety/tyrell)<a href="https://agentmods.dev/plugins/ogrodev/fsociety/tyrell"><img src="https://agentmods.dev/badge/plugins/ogrodev/fsociety/tyrell/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/plugins/ogrodev/fsociety/tyrell"><img src="https://agentmods.dev/badge/plugins/ogrodev/fsociety/tyrell.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tyrell 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 2mo 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.
What it actually says
{
"name": "tyrell",
"description": "Tyrell — leak database hunter plugin with Hexstrike MCP integration for Kali Linux. Exposed database discovery, data acquisition, cross-plugin pipeline to elliot.",
"source": "./tyrell/",
"author": {
"name": "Ogrodev"
}
}What it installs
The manifest is a name and a version. 5 skills, 16 commands, 2 agents travel with it, and installing the plugin installs all of them — 2,016 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill source-intelligence A 343 tokens
- Skill cross-plugin-pipeline A 284 tokens
- Skill exposed-databases A 253 tokens
- Skill leak-hunting A 330 tokens
- Skill data-acquisition A 96 tokens
- Command ty-classify A 14 tokens
- Command ty-handoff A 12 tokens
- Command ty-acquire A 9 tokens
- Command ty-campaign A 10 tokens
- Command ty-forums A 9 tokens
- Command ty-hunt A 13 tokens
- Command ty-planner A 7 tokens
- Command ty-telegram A 10 tokens
- Command ty-dork A 12 tokens
- Command ty-shodan A 12 tokens
- Command ty-status A 13 tokens
- Command ty-sources A 14 tokens
- Command ty-install A 7 tokens
- Command ty-profile A 17 tokens
- Command ty-darkweb B 17 tokens
- Command ty-github C 15 tokens
- Agent joanna A 307 tokens
- Agent scott A 212 tokens
What ships with it
1 file beside marketplace.json#tyrell 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.
- 2mo ago First seen · 8 lines scan A 810887de8079
tyrell is a plugin published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
ecto
Compatibility namespace for the Elixir/Phoenix plugin's /ecto: commands.
dex
Analytics engineering for Claude Code and any agent: data warehouse exploration, dbt transformation and semantic modeling, and schema-drift maintenance on dbt.
mirrord
Connect your agent to a live Kubernetes cluster with mirrord, so it tests code changes against real services. Covers setup, config, CI, database branching, queue splitting, and preview environments.
databases
Database experts for SQL, NoSQL, graph databases, and vector databases. Includes Postgres, MongoDB, Neo4j, Cassandra, MariaDB, and vector DB specialists.
sql-safety-net
Static, no-database-connection guardrails for schema and query work: rewrites unsafe migrations into zero-downtime expand-contract steps, hunts ORM N+1 queries in your diff, interprets pasted EXPLAIN plans, and flags schema anti-patterns.
sql
SQL specialist: query optimization, schema and index design, execution-plan analysis, and platform-specific features across PostgreSQL, MySQL, SQL Server, SQLite, and Oracle.