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 singula-ai/alego --skill cordis-composition-referencegit clone --depth 1 https://github.com/singula-ai/alegoWrote 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/singula-ai/alego/cordis-composition-reference)<a href="https://agentmods.dev/skills/singula-ai/alego/cordis-composition-reference"><img src="https://agentmods.dev/badge/skills/singula-ai/alego/cordis-composition-reference/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/singula-ai/alego/cordis-composition-reference"><img src="https://agentmods.dev/badge/skills/singula-ai/alego/cordis-composition-reference.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.00059 | $0.00640 |
| Opus 5.5 | $0.00024 | $0.00256 |
| Sonnet 5.5 | $0.00012 | $0.00128 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
cordis-composition-reference 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 17d 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.
This is a copy
97% identical to cordis-composition-reference — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cordis composition reference
Reference material for bundle patches and preset plugin lists. Procedures live in cordis-plugin-development and editing-cordis-compositions.
Loader patch dialect
A profile composes an ordered list of patch layers over the bundle entry lists. Each patch is a mapping:
insert: [rows]appends rows; with anidnaming an existinggroup: truerow, the rows are appended inside that group'sconfiglist.- A patch with an
idand noinserttargets the existing row with that id. Supplied fields replace the row's fields;configis replaced wholesale, never deep-merged, so restate every field the row needs. A truthynameasserts the existing plugin name rather than renaming it. - Non-insert patches without a nonempty
id, and targets that match no row, are warned about and skipped.
A row has id, name (the plugin package specifier; inserted relative paths are anchored beside their patch file), optional config, and optional disabled, inject, intercept, and isolate.
group: truewithname: cordis:groupmakesconfiga nested entry list and allows patches to insert into it by id.cordis:includeloads a literal YAML or JSON entry list fromconfig.path.disabledaccepts a boolean, null, or a!!jsexpression evaluated against the Loader context at every mount decision. A disabled row omits requiredconfigunlessgroup: trueforces activation.!!jsscalars are Loader expressions, never!js. Insideconfigthey are evaluated after the row's declared injections activate, against that plugin's context (ctx.<service>), so!!js alegoHomePath('sessions')and!!js "!ctx.get('profileContext')"are valid. Other row metadata stays literal.isolatemaps service names totrueor a realm label; a preset plugin that provides a service isolates the provider and all consumers together. Scope controls contributions and event visibility;isolatecontrols service instances.
plugin_manager list_plugins reports each row's enabled flag and fiberPhase; set_plugin and set_bundle answer overridden when a higher-priority layer wins.
What ships with it
1 file 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.
- 17d ago First seen · 30 lines · 59 tokens per session scan A e15f5ac0e6ce
cordis-composition-reference is a skill published in the GitHub repository singula-ai/alego (109 stars, last pushed 17d ago), licensed MIT. It adds 59 tokens to every session and 640 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to cordis-composition-reference, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
ctx
Codebase intelligence and evidence-driven governance with the indexed ctx CLI. Use when exploring an unfamiliar repository, locating symbols or callers, checking for existing implementations, estimating change impact, enforcing architecture rules, scoring a branch, finding hotspots or duplication, or analyzing…
ctx
Codebase intelligence and evidence-driven governance with the indexed ctx CLI. Use when exploring an unfamiliar repository, locating symbols or callers, checking for existing implementations, estimating change impact, enforcing architecture rules, scoring a branch, finding hotspots or duplication, or analyzing…
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
agent-harness-testing
A testing method for coding tasks in unfamiliar projects. It first discovers how the project is tested, then uses a failing check followed by a passing check to verify a change.
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.