Agentlas OS is a local-first system for creating, storing, borrowing, and running specialist AI agents and temporary agent teams through supported hosts and models. It serves people who want reusable agents that remain available across computers and model workspaces, and the catalogue contains its skills, commands, hooks, agents, instructions, plugin, and rule.
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 agentlas-ai/Agentlas-OS --skill routing-card-authoringgit clone --depth 1 https://github.com/agentlas-ai/Agentlas-OSWrote 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/agentlas-ai/agentlas-os/routing-card-authoring)<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-os/routing-card-authoring"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-os/routing-card-authoring/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/agentlas-ai/agentlas-os/routing-card-authoring"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-os/routing-card-authoring.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.00068 | $0.02160 |
| Opus 5.5 | $0.00027 | $0.00864 |
| Sonnet 5.5 | $0.00014 | $0.00432 |
| Haiku 4.5 | $0.00007 | $0.00216 |
Grade A, and why
routing-card-authoring 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 11d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Routing Card Field Spec — what goes in every field, and where it lands
One card, four builders. 10-single-agent-builder, 20-multi-agent-team-builder,
30-agentlas-packager, and 40-session-agent-builder differ in what they
assemble, but the routing card is the same artifact with the same rules in all
four. This file is the reference
they share, and templates/routing-card.example.json is a complete card that
passes schemas/routing-card.schema.json.
Why the fields behave the way they do
The real matching is sentence-to-sentence. The slot's task text is
compared semantically against the card's summary. A card whose summary
names its actual deliverable outranks a card with a perfect id list.
So the card has two jobs, and mixing them is the classic defect: short ids for retrieval, whole sentences for judgement. A sentence that leaks into an id field becomes a slug nothing else can ever match.
Field table
Columns: what the field is for · what the hub does with it · what to write.
Identity and display
| Field | Hub use | What to write |
|---|---|---|
schemaVersion |
none | Exactly "routing-card/2.0". |
card_version |
none | Semver of this card's content, bumped when you edit it. |
id |
identity | local/<package-slug> before upload. |
canonical_id |
identity | Stable cross-registry id when one exists, else omit. |
type |
hard filter (entityKind) |
"agent", "team", or "plugin". A team means an orchestrator owns workers; do not label a single worker a team. |
name / name_ko |
display + lexical retrieval | The job title a human would search for. Not a product pun. |
aliases |
lexical retrieval | Other phrasings a requester might type, including Korean. Cheap and safe to add. |
supersedes |
lineage | Ids this card replaces. |
The sentences that actually win matches
| Field | Hub use | What to write |
|---|---|---|
summary (≤240 chars) |
semantic ranking against the slot task — the single highest-value field | One sentence: what it does, what the requester ends up holding, and the one boundary that matters. Name the deliverable in the words a requester would use. Do not list technologies for their own sake. |
summary_ko |
display + Korean retrieval | Faithful Korean of summary. |
description |
semantic ranking | 2–4 sentences: when to use it, what the deliverable contains, and what it explicitly does not do. This is where "does not implement" or "does not run migrations" belongs. |
trigger_examples |
semantic ranking (strong) | 6+ real sentences a requester would actually type, 3 Korean and 3 English. Write the request, not a feature name. |
anti_triggers |
negative ranking | 4+ sentences that look adjacent but must NOT route here. This is how a design agent stops absorbing implementation work. |
known_failure_cases |
honesty, read by the host LLM | What the agent degrades to when an input is missing. Sentences, whole. |
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.
- 11d ago Changed · -37 lines b8c286418c78
- 1mo ago First seen · 154 lines · 68 tokens per session scan A e477a41330b5
routing-card-authoring is a skill published in the GitHub repository agentlas-ai/Agentlas-OS (1,584 stars, last pushed 2d ago), licensed Apache-2.0. It adds 68 tokens to every session and 2,160 once invoked, about $0.0003 per session on Opus 5.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
yait-aichain
Build AI features in Python — an LLM call, a multi-step pipeline, the same work over many items, or an agent that uses tools (web search, page fetching, your own functions, any REST API or MCP server, a working folder), asks a human before risky actions, stays within a money budget, or pauses and resumes — on any…
yait-aichain
Build AI features in Python — an LLM call, a multi-step pipeline, the same work over many items, or an agent that uses tools (web search, page fetching, your own functions, any REST API or MCP server, a working folder), asks a human before risky actions, stays within a money budget, or pauses and resumes — on any…
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.
a2ui
Make a reply easier to read and act on with rich blocks inside ordinary Markdown — a choice the user picks from, a form that collects several answers, a procedure as steps with warnings in place, a callout, a Mermaid diagram, a weather card, a live clock or countdown, a dashboard of gauges for a quota, a budget or a…