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/lixin97/agora-lab/shared-referencesnpx skills add LiXin97/agora-lab --skill shared-referencesgit clone --depth 1 https://github.com/LiXin97/agora-labWrote 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/lixin97/agora-lab/shared-references)<a href="https://agentmods.dev/skills/lixin97/agora-lab/shared-references"><img src="https://agentmods.dev/badge/skills/lixin97/agora-lab/shared-references.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.1 | $0.00032 | $0.00171 |
| Opus 5 | $0.00016 | $0.00086 |
| Sonnet 5 | $0.00006 | $0.00034 |
| Haiku 4.5 | $0.00003 | $0.00017 |
Grade A, and why
shared-references 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 6d 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
Shared References
This directory is a shared standards library. It exists so role skills can point to one source of truth instead of duplicating policy.
Reference Documents
reviewer-independence.mdevidence-standards.mdmeeting-rubric.mdhandoff-checklist.mdwriting-principles.mdvenue-checklists.mdcitation-discipline.md
Usage
Role-specific skills should cite these files explicitly whenever they talk about:
- independent review
- claim/evidence alignment
- handoff quality
- meeting quality
- writing discipline
- venue readiness
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 30 lines · 32 tokens per session scan A 12b2fba52bd3
shared-references is a skill published in the GitHub repository LiXin97/agora-lab (49 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 171 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-08-30.
Other skills, from other repositories
speckit.clarify
Skill "speckit.clarify" from caipe-io/ai-platform-engineering, covering user input and outline.
speckit.specify
Skill "speckit.specify" from caipe-io/ai-platform-engineering, covering user input, outline, quick guidelines, section requirements and for ai generation.
update-docs
Audit and update all documentation moving parts for ai-platform-engineering. Checks release blog posts, features page, agent docs, homepage version strings, Docusaurus version config, and sidebar completeness. Fixes what is stale and reports what needs manual attention. Use after cutting a release, adding a new agent…
docker-compose-first-install
Validate and repair the OSS first-install Docker Compose path. Use when editing docker-compose.yaml, docker-compose.dev.yaml, .env.example, release image tags, Compose profiles, Keycloak/OpenFGA/RAG defaults, or first-launch UI behavior for local all-in-one installs.
speckit.plan
Skill "speckit.plan" from caipe-io/ai-platform-engineering, covering user input, outline, phases, phase 0: outline & research and phase 1: design & contracts.
speckit.sync-template
Skill "speckit.sync-template" from caipe-io/ai-platform-engineering, covering user input, outline, step 1 — read current state, step 2 — discover latest release and step 3 — read the manifest.