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 skills/opensupplyhub/open-supply-hub/explain-codenpx skills add opensupplyhub/open-supply-hub --skill explain-codegit clone --depth 1 https://github.com/opensupplyhub/open-supply-hubWrote 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/opensupplyhub/open-supply-hub/explain-code)<a href="https://agentmods.dev/skills/opensupplyhub/open-supply-hub/explain-code"><img src="https://agentmods.dev/badge/skills/opensupplyhub/open-supply-hub/explain-code.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.00059 | $0.00785 |
| Opus 5 | $0.00030 | $0.00392 |
| Sonnet 5 | $0.00012 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
explain-code 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explaining OS Hub Code and Systems in Plain English
This skill translates anything technical at OS Hub into language the reader can use — a single file, an API endpoint, a database table, a lambda function, or how a whole system fits together.
Step 1 — Confirm experience level (one-time per session)
If unknown from earlier in the session, ask:
Quick question so I pitch this right:
- New to code — plain English with real-world analogies
- Some technical comfort — terms are okay, explain non-obvious ones
- Engineer — full technical depth, no analogies needed
Which fits? (1, 2, or 3)
Step 2 — Ground the answer in real code
Always read the actual source before explaining. Three cases:
- The user pasted code or named a specific file/function → read it directly.
- The user asked about a system, endpoint, lambda, or concept without pointing at specific code → search the OS Hub repo first to find the real implementation, then read it.
- The request is still vague after you look → ask one clarifying question.
If something touches multiple layers (e.g., a lambda that hits the API and the database), read each layer.
Step 3 — Answer short, pull in only the sections that fit
Default response is concise — aim for under 200 words. Lead with the takeaway, then offer to go deeper. Use only the sections below that the question actually calls for. Don't inflate.
Available sections:
Infrastructure
Where this runs and what it's built on (Django service, AWS Lambda, Kafka consumer, RDS table, S3 bucket, etc.). Use when the platform matters for the explanation.
Big Picture
One or two sentences: what this does and where it lives in OS Hub.
Main Parts
2-4 bullets describing the major pieces. Use when the thing has internal structure worth walking through.
Analogy
Real-world comparison that makes the concept stick. Especially valuable for Level 1 readers.
Examples:
- "Think of this like a gatekeeper — it checks credentials before letting requests through"
- "This is the recipe card — it lists ingredients and the order to combine them"
- "Picture a referee at a basketball game — this watches the action and flags anything off"
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.
- 4d ago First seen · 78 lines · 59 tokens per session scan A a9321dae58bd
explain-code is a skill published in the GitHub repository opensupplyhub/open-supply-hub (20 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 785 once invoked, about $0.0003 per session on Opus 5. 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 skills, from other repositories
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
moderator-page-migration
Port a moderator page from the main Next.js app (src/pages/moderator/) into apps/moderator. Use when asked to migrate, move or cut over a /moderator/ page to the spoke, or to port its tRPC procedures and Prisma services to SvelteKit loads/actions and Kysely.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
sql-translate
Translate SQL queries between database dialects (Snowflake, BigQuery, PostgreSQL, MySQL, etc.).