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.02698 |
| Opus 5 | $0.00034 | $0.01349 |
| Sonnet 5 | $0.00014 | $0.00540 |
| Haiku 4.5 | $0.00007 | $0.00270 |
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 — 154 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
Every rule below was measured against the live corpus on 2026-07-30 (492 workforce profiles, 253 stored manifests). The two facts that decide everything else:
- Only two columns can be compared between a work order and a card.
communities(422 of 492 populated, 105 distinct) andskills(492 of 492, 1,969 distinct). Everything else is either declared by almost nobody (roles6,tools10,knowledge0,forbiddenAuthorities0), or declared by everyone with the same value (runtimes14 distinct over 492 profiles,languagesexactly 2,modalitiesexactly 1) — neither can separate candidates. - The real matching is sentence-to-sentence. The slot's
tasktext is compared semantically against the card'ssummary. 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 — measured: 8,973 distinct
outputs values across the corpus, 0% shared by two agents.
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. |
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 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,109 stars, last pushed 4d ago), licensed Apache-2.0. It adds 68 tokens to every session and 2,698 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
agentfield-use
Whenever you have a discrete task to perform — one the user delegated, or one that arose inside your own work — check FIRST whether an installed AgentField agent covers it, and offload to it by default when one does. Coverage, not task size, is the test: even a small job goes to a covering agent. The check is cheap …
agent-optimization
Improve an Agent State through versioned scores and score-linked Traces from a frozen Benchmark.
quality-loop
Use this workflow recipe when a draft, plan, proposal, or other deliverable should be independently reviewed and revised until it satisfies explicit quality criteria.
cli-skill-design
Design a co CLI surface and its SKILL.md together so an agent can drive it without guessing — every command ends by naming the next one, --help lists everything, and every failure says what to run instead. Use when adding a new CLI command group, writing or rewriting a SKILL.md for one, or auditing an existing one.
update-setup
A one-time setup wizard for creating a personalised upgrade guide for a workspace. It checks for an existing guide, identifies the current version and installation clues, and requires confirmation of the installation method before writing a new guide.
skill-creator
Create, edit, improve, tidy, review, audit, or restructure memmy-agent skills and SKILL.md files.