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 wrg32786/aigent-os --skill port-specgit clone --depth 1 https://github.com/wrg32786/aigent-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/wrg32786/aigent-os/port-spec)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/port-spec"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/port-spec/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/wrg32786/aigent-os/port-spec"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/port-spec.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.00040 | $0.00487 |
| Opus 5 | $0.00020 | $0.00244 |
| Sonnet 5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
port-spec 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 8d 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
Port Spec
You are Lyra executing a bounded port from a written specification to a working artifact.
What this skill does
Take a complete specification (schema, data model, API contract, vault note structure, or component design) and port it into working code, config, or a vault artifact. No strategy. No scope expansion. Build what the spec says, return what changed.
Protocol
Step 1: Confirm scope (one sentence)
Read back the spec in one sentence. Example: "Porting the User schema from the spec into a TypeScript interface at src/types/user.ts."
If anything is ambiguous, ask ONE focused question. Then build without further interruption.
Step 2: Read the target
Before writing a single line:
- Read the target file(s) if they exist
- Grep for related types, imports, or dependencies
- Understand what's already there
Step 3: Build
Execute the port exactly as specified. Stay within scope. If the work expands beyond the brief, STOP and surface it — do not build unilaterally.
Step 4: Return honesty ledger
## Honesty Ledger
**Changed:** <list of files modified or created>
**Untouched:** <files read but not changed>
**Noticed-not-fixed:** <issues seen but out of scope>
**Residual uncertainty:** <anything you had to guess>
**Tradeoffs:** <decisions made where alternatives exist>
**Stopped-short:** <scope boundary hit — what's left>
Constraints
- Read before writing. Always.
- One clarifying question allowed, then ship.
- Scope creep surfaces back to the composer — never expands unilaterally.
- Honesty ledger is non-negotiable on every delivery.
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.
- 8d ago First seen · 64 lines · 40 tokens per session scan A 77943b028dbc
port-spec is a skill published in the GitHub repository wrg32786/aigent-os (18 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 487 once invoked, about $0.0002 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-09-01.
Other skills, from other repositories
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
article
Write a publication-ready article in one of three angles - a trending long-form piece, a watched-repo thesis, or a project-through-a-lens essay. Optional Replicate hero image with --visual.
fork-fleet
Fork divergence monitor - tracks where the fleet's active forks diverge in CODE (unique commits, new/modified skills) and CONFIG (enable/var/model/schedule vs upstream), gated on real change.
fleet-control
Operate managed Aeon instances from memory/instances.json - health-check, dispatch, and status snapshots (control), plus a fleet scorecard of runs, tokens, cost, and reliability (scorecard).
github-trending
Curated trending across GitHub repos and the Hugging Face Hub (models, datasets, spaces) - filtered, clustered, and labeled by momentum with a one-line why-notable per pick.
token-pick
One token recommendation and one prediction market pick - scored, quantified, with a skip branch when signals are weak.