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/akram012388/cc-dm/registernpx skills add Akram012388/cc-dm --skill registergit clone --depth 1 https://github.com/Akram012388/cc-dmWrote 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/akram012388/cc-dm/register)<a href="https://agentmods.dev/skills/akram012388/cc-dm/register"><img src="https://agentmods.dev/badge/skills/akram012388/cc-dm/register.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.00061 | $0.00760 |
| Opus 5 | $0.00030 | $0.00380 |
| Sonnet 5 | $0.00012 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
register 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Register Session
Register this session with a user-chosen name, role, and optional project tag.
Arguments (fast path)
If arguments are provided (e.g., name: planner | role: worker | project: myapp):
- Parse the provided name, role, and project from the arguments.
- Skip the pre-check gate and interactive prompts entirely.
- Call the
registertool directly with the provided values. - If the tool returns an error (e.g., name in use), report it clearly.
- If successful, confirm: "Registered as {name} with role {role}." If a project was set, add: "Broadcasts and DMs scoped to project {project}."
- Stop here — do not proceed to the pre-check or interactive registration.
Pre-check (gate)
Before prompting the user, determine if registration is needed:
- Read your session id from the MCP server instructions (the
"Your session id is ..."line). - Call the
whotool to list active sessions. - Find your session id in the results.
- If your session's
nameis different from your session id (i.e. notsession-XXXXXX), registration was already done AND no arguments were provided. Stop here silently — do not prompt the user. - If your session is not found or its name still equals the auto-generated id, proceed to registration.
- If your session's
Registration steps
- Ask the user: "What session name would you like to use?" (e.g., planner, backend, reviewer, tests)
- Wait for their response.
- Before proceeding, check the
whoresults from the pre-check. If the requested name is already taken by another session, tell the user: "That name is already in use." Show the active session list and ask them to pick a different name. Repeat until available. - Ask the user: "What role should this session have?" (e.g., orchestrator, worker, reviewer, specialist)
- Wait for their response.
- Ask the user: "What project tag should this session use? (optional — if set, broadcasts will be scoped to this project only)"
- If there are active sessions with non-empty project tags, list the distinct project tags: "Active projects:
myapp,api-server. You can pick one of these or enter a new one." - The user can leave this blank for no project (global broadcasts).
- If there are active sessions with non-empty project tags, list the distinct project tags: "Active projects:
- Wait for their response.
- Call the
registertool with the providedname,role, andproject(if given). - If the tool returns an error about the name being in use, it may be a stale session from a previous
/resumeor/clear. Tell the user: "That name is held by a stale session that will expire within 60 seconds. Wait and retry, or pick a different name." Show the active session list. - Confirm success: "Registered as {name} with role {role}." If a project was set, add: "Broadcasts and DMs scoped to project {project}."
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 · 46 lines · 61 tokens per session scan A 9f345cbad087
register is a skill published in the GitHub repository Akram012388/cc-dm (22 stars, last pushed 5mo ago), licensed MIT. It adds 61 tokens to every session and 760 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
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
sdk-design
Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…