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/jacobfunch/usefilloWrote 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/jacobfunch/usefillo/fillo)<a href="https://agentmods.dev/plugins/jacobfunch/usefillo/fillo"><img src="https://agentmods.dev/badge/plugins/jacobfunch/usefillo/fillo/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/jacobfunch/usefillo/fillo"><img src="https://agentmods.dev/badge/plugins/jacobfunch/usefillo/fillo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fillo 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 1mo 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": "fillo",
"displayName": "Fillo",
"description": "Build hosted and native product forms with Fillo from your coding agent.",
"version": "0.1.0",
"author": {
"name": "Fillo",
"url": "https://fillo.so"
},
"homepage": "https://fillo.so/agents",
"repository": "https://github.com/jacobfunch/usefillo",
"license": "MIT",
"keywords": ["forms", "file-requests", "uploads", "headless-forms", "react", "agents"]
}
What it installs
The manifest is a name and a version. 1 skill, 1 MCP server travel with it, and installing the plugin installs all of them — 115 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 15 lines scan A 60bd2677e5f2
fillo is a plugin published in the GitHub repository jacobfunch/usefillo (0 stars, last pushed today), 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-08-30.
Other plugins, from other repositories
azure-sdk-dotnet
Azure SDK patterns and best practices for .NET developers covering AI, resource management, identity, messaging, and Key Vault libraries.
data-table-filters
Install and wire up data-table-filters — filterable, sortable React data tables with server-side filtering, faceted counts, infinite scroll, and virtualization, delivered as shadcn registry blocks.
walkeros
Skills and MCP tools for walkerOS - the open-source event data collection platform. Learn architecture, create sources/destinations/transformers, validate events, bundle flows locally, and manage projects and deployments through the hosted walkerOS MCP server.
app-builder
Development, customization, testing, and deployment skills for Adobe App Builder projects, including the Workfront UI-extension suite (skills/appbuilder-workfront).
ring-dev-team
24 specialized developer agents + 35 development skills. Backend (Go/TypeScript) and frontend (React/Next.js) dev cycles, DevOps, QA, SRE, and the parallel code-review pool.
strapi-plugin-dev
Strapi v5 plugin development — Document Service API, factory patterns, RHF+Zod, TanStack Query v5. Includes auto-firing hooks (anti-pattern detection, schema validation, context injection), slash commands (/strapi-scaffold-plugin, /strapi-add-content-type, /strapi-add-cm-panel, /strapi-verify), and a strapi-reviewer…