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 Bilal140202/the-lord-of-the-skills --skill nickodemusrr__antigravity-tutorialgit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-skillsWrote 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/bilal140202/the-lord-of-the-skills/nickodemusrr__antigravity-tutorial)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/nickodemusrr__antigravity-tutorial"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/nickodemusrr__antigravity-tutorial/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/bilal140202/the-lord-of-the-skills/nickodemusrr__antigravity-tutorial"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/nickodemusrr__antigravity-tutorial.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00013 | $0.00895 |
| Opus 5 | $0.00006 | $0.00447 |
| Sonnet 5 | $0.00003 | $0.00179 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
orchestration 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 9d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Voyager Multi-Agent Orchestration
1. Project Overview
Voyager is a "Retro-Future" arcade space exploration game. Players pilot a craft, as Astronaut 311-C, to connect stars in Zodiac constellations within a shrinking time limit. If they connect all 12 constellations in time, they make friends with Zarg 966-Z, from Zargaborg. Players' completion times are scored in a leaderboard.
Three agents will collaborate to build this game. Agent A will build the game engine. Agent B will build the leaderboard. Agent C will validate their code by testing gameplay.
2. Technical Architecture and Ownership
Voyager is built on the following tech stack:
-
HTML5 Canvas: High-performance 2D rendering.
-
Vanilla JavaScript: Core game loop, physics, and state management.
-
CSS3: Retro UI overlays and typography.
-
Firebase: Easy hosting, authentication, and data persistence.
To prevent file collisions, the project is split into three primary functional domains:
-
Agent A (Core Engine): Creates and owns
public/game.js. Responsible for the game loop, physics, constellation data, and local state. -
Agent B (Social and Persistence): Creates and owns
public/leaderboard.js. Responsible for Firebase initialization, Firestore queries, and high-score UI management. -
Agent C (Validation): Responsible for validating the functionality and interoperability of the code generated by Agents A and B. Uses gameplay to identify issues. Reads and writes any necessary file.
-
Shared Resources (
public/index.htmlandpublic/style.css): Agent A creates these files. All agents are authorized to read and write to these files.
3. The "Global Bridge" (Communication Contract)
Agents A and B must use a shared global object, window.Voyager, to coordinate state transitions without direct file dependency.
-
State Enum: Use shared states:
START,PLAYING,FAIL,WIN,LEADERBOARD. -
Hand-off Logic: When a game ends,
game.jswill callwindow.Voyager.showLeaderboard(score).
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.
- 9d ago First seen · 97 lines · 13 tokens per session scan A d6bc0db0f950
orchestration is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 895 once invoked, about $0.0001 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-03.
Other skills, from other repositories
serpsmith
Publish SEO articles reliably across AI-agent runtimes.
diagnosing-bgs-problems
A symptom-first guide for investigating crashes, frame-rate drops, stuttering, freezes, and startup failures in Bethesda Game Studios games with mods.
ai-behavior-trees-utility-ai
Build a production behavior-tree runtime (Blackboard, action/condition leaves, sequence/selector/parallel composites, decorators) and a Utility AI system (response curves — linear, exponential, sigmoid, quadratic — considerations, and action evaluators), plus hybrid BT-drives-Utility agents. Use when implementing a…
godot-multiplayer
Build networked games with Godot 4.7 high-level multiplayer: set up an ENetMultiplayerPeer server/client, define RPCs with the @rpc annotation (call via rpc()/rpcid()), set per-node multiplayer authority, and replicate state with MultiplayerSpawner and MultiplayerSynchronizer. Use when adding multiplayer/networking to…
godot-physics
Use Godot 4.7 physics bodies and detection in 2D and 3D: RigidBody, StaticBody, Area, and CharacterBody; collision layers vs masks; contact/overlap signals; and raycasts (RayCast nodes and direct space-state queries). Use when configuring collision layers/masks, detecting overlaps with Area2D/Area3D, applying forces…
game-jam
Plan and ship a game under a jam deadline: lock scope to the clock, schedule the hours, cut features, and submit on time. Use for a game jam (Ludum Dare, GMTK Jam, Global Game Jam), a 48-hour or weekend build, or scoping and submitting a jam entry.