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 skills add mpazik/Binder --skill binder-appgit clone --depth 1 https://github.com/mpazik/BinderWrote 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/skills/mpazik/binder/binder-app)<a href="https://agentmods.dev/skills/mpazik/binder/binder-app"><img src="https://agentmods.dev/badge/skills/mpazik/binder/binder-app/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/skills/mpazik/binder/binder-app"><img src="https://agentmods.dev/badge/skills/mpazik/binder/binder-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00074 | $0.02630 |
| Opus 5.5 | $0.00030 | $0.01052 |
| Sonnet 5.5 | $0.00015 | $0.00526 |
| Haiku 4.5 | $0.00007 | $0.00263 |
Grade A, and why
binder-app scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. `curl http://127.0.0.1:4000/api/schema` returns JSON. How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Binder App
Scaffold a small browser app served by binder http, on top of an existing Binder workspace. Default to plain HTML + vanilla JS, no build step, CDN libraries only when they save real work.
When to use
User asks for a UI on top of their Binder data. Typical asks:
- "Create a dashboard of my transactions over time."
- "Build a kanban board of tasks grouped by status, drag and drop like Trello."
- "Make a small admin panel for my contacts."
- "Show me a chart of X grouped by Y."
If the user wants to query data without a UI, send them to the binder-cli skill instead.
Workflow
1. Read the schema
Always start here. Do not guess type or field names.
binder schema # all types and fields
binder schema --types Task # one type
Note for each type the user mentioned: required fields, allowed values for enum-like fields (only: [...]), and relation targets. Allowed values matter for kanban columns, chart axes, filters.
2. Plan, or ask
Before writing code, produce a short plan: what records get queried, how they get grouped or aggregated, what writes (if any) the UI performs, and which CDN libs (if any) you'll pull in.
Ask the user a clarifying question when any of these is unclear:
- Which type(s) to show, if the workspace has several plausible candidates.
- Which field drives grouping or the time axis (e.g.
createdAtvs a domain field likedate). - Whether the UI is read-only or should write back (drag-and-drop status changes, edits, creates).
- Bucket granularity for time series (day/week/month).
Keep the plan to a few bullets. Do not ask more than two or three questions.
3. Decide: client-only or server.ts
Default to client-only. The built-in API is enough for most cases.
Add .binder/web/server.ts only when one of these is true:
- The aggregation is too heavy or awkward to do in the browser.
- You need an endpoint that talks to an external service (webhook, third-party API).
- You need a custom shape that combines multiple queries server-side.
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 · 291 lines · 74 tokens per session scan A ec2dfac63b63
binder-app is a skill published in the GitHub repository mpazik/Binder (40 stars, last pushed 28d ago), licensed MIT. It adds 74 tokens to every session and 2,630 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agentmemory-rest-api
The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server. Use when calling agentmemory over HTTP, when MCP is unavailable and you need a fallback, or when integrating a host that does not speak MCP.
engraphis-memory
Give the agent durable, scoped, explainable memory across sessions and repositories through the Engraphis MCP tools. Use when you learn a convention, decision, bug cause/fix, or user preference worth keeping; when prior context would help before you answer or act (to avoid re-asking or re-deriving); when asked "why is…
starcat-weekly-import
A tool for turning news, project lists, and other bulk text into verified GitHub repository links, then adding confirmed repositories to Starcat Weekly. It checks that each link belongs to the actual project owner.
starcat-support-project-create
A guided process for creating a separate support project under the Starcat codebase, such as an API, command-line tool, browser extension, website, or documentation project. It also registers the project with the wider Starcat system.
starcat-backend-release
A release procedure for Starcat's separate backend API repositories, including services for sharing, trends, weekly data, the wiki, recommendations, and discovery. It covers version tags, pull requests, automated workflows, and Fly.io deployments.
starcat-supports-ops
A set of procedures for running and maintaining Starcat’s self-hosted Go services locally and on Fly.io, a cloud hosting platform. It covers service status, health checks, secrets, backups, and data restoration.