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/referodesign/refero_skillWrote 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/mcp/referodesign/refero_skill/refero)<a href="https://agentmods.dev/mcp/referodesign/refero_skill/refero"><img src="https://agentmods.dev/badge/mcp/referodesign/refero_skill/refero/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/mcp/referodesign/refero_skill/refero"><img src="https://agentmods.dev/badge/mcp/referodesign/refero_skill/refero.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
refero 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
{
"refero": {
"type": "http",
"url": "https://api.refero.design/mcp"
}
}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 · 6 lines scan A b3d7a9d65bee
refero is an MCP server published in the GitHub repository referodesign/refero_skill (325 stars, last pushed 8d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
Figma-Context-MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot. Runs locally from the figma-developer-mcp npm package. Needs 1 environment variable to run.
figma-mcp-bridge
MCP server "figma-mcp-bridge" as configured in atezer/FMCP. Runs /REPLACE/WITH/ABSOLUTE/PATH/TO/FCM/dist/local-plugin-only.js with node. Needs 1 environment variable to run.
canicode
Analyze Figma designs for dev & AI readiness. 39 rules, scoring, HTML reports. Runs locally from the canicode npm package. Needs 1 environment variable to run.
figma-unlimited-mcp
MCP server that lets an AI agent read and edit FigJam boards through a local Figma plugin — no REST or Dev Mode quotas. Runs locally from the figma-unlimited-mcp npm package.
tldraw
MCP server "tldraw" as configured in Mihai-Codes/tldraw-mcp-server. Runs dist/index.js with node. Needs 1 environment variable to run.
hermes-pen-bridge
Hermes-first MCP bridge for the Pencil design tool — proxies the bundled MCP server and adds .pen file utilities. Runs locally from the hermes-pen-bridge Python package.