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 Qiushen-first/cn-investment-banking-skills --skill cn-ib-document-controlgit clone --depth 1 https://github.com/Qiushen-first/cn-investment-banking-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/qiushen-first/cn-investment-banking-skills/cn-ib-document-control)<a href="https://agentmods.dev/skills/qiushen-first/cn-investment-banking-skills/cn-ib-document-control"><img src="https://agentmods.dev/badge/skills/qiushen-first/cn-investment-banking-skills/cn-ib-document-control/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/qiushen-first/cn-investment-banking-skills/cn-ib-document-control"><img src="https://agentmods.dev/badge/skills/qiushen-first/cn-investment-banking-skills/cn-ib-document-control.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.00115 | $0.00930 |
| Opus 5 | $0.00057 | $0.00465 |
| Sonnet 5 | $0.00023 | $0.00186 |
| Haiku 4.5 | $0.00012 | $0.00093 |
Grade A, and why
cn-ib-document-control 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 13d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CN IB Document Control
Create one auditable register that answers: what is required, what has been received, in what form, which version is current, who owns the gap, and what evidence closes it.
Principles
- Never equate
receivedwithcomplete,valid,signed,original, orreviewed. - Track each independently controlled item as a separate row.
- Preserve issuer/entity, document period, required form, and version.
- Do not delete superseded records. Mark them superseded and link the replacement.
- Close an item only with reviewable closure evidence.
- Do not upload or commit confidential deal materials to a public repository.
Workflow
1. Define the register scope
Identify:
- transaction and workstream;
- entities and persons covered;
- applicable period;
- source of the requirement;
- expected document form;
- responsible party and reviewer;
- delivery deadline and critical-path dependency.
Read references/document-categories.md to choose categories. Do not force unrelated items into a generic other bucket without explanation.
2. Create the register
Start with assets/document-control-template.csv or reproduce the same fields in an XLSX workbook.
Use a stable document_id. Keep the ID after revisions. Create a new row only when the controlled requirement is distinct.
Minimum fields:
document_id, category, document_name, entity, period,
requirement_source, required_form, version, status,
original_status, signature_status, seal_status, scan_status,
owner, reviewer, due_date, source_path, closure_evidence, notes
3. Apply controlled statuses
Read references/status-taxonomy.md. Track independently:
- overall workflow status;
- original received;
- signatures complete;
- seal complete;
- scan quality;
- review status;
- superseded status.
Avoid free-text statuses such as 差不多, 应该齐了, or 最新.
4. Reconcile received materials
For each delivery:
- match it to an existing requirement;
- confirm entity, person, period, document type, and version;
- inspect completeness, signatures, seals, pages, color, legibility, and validity period;
- record the source location without moving the original unless instructed;
- update the register and reviewer;
- create a new gap when the file only partially satisfies the requirement.
What ships with it
5 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.
- 13d ago First seen · 122 lines · 115 tokens per session scan A de21e139dee4
cn-ib-document-control is a skill published in the GitHub repository Qiushen-first/cn-investment-banking-skills (101 stars, last pushed 26d ago), licensed Apache-2.0. It adds 115 tokens to every session and 930 once invoked, about $0.0006 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
html-ppt-zhangzara-stencil-tablet
A workplace-safety compliance review for a manufacturing regulator — findings, the evidence chain, and the corrective mandate. Built as a decision-grade policy briefing deck for regulator, plant leadership.
treatment-plans
Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and…
handbook-updates
Diff a proposed handbook change against the current version, flag ripple effects and state supplement impacts. Use when user says "update the handbook", "add this to the handbook", "handbook change", or has a policy ready for insertion.
software-copyright-materials
A workflow for creating Chinese application materials for software copyright registration from a real software project.
iflytek-contract-intelligence-review
A contract-review workflow for scanned or digital agreements. It can recognize document text, examine clauses, detect risks, check compliance, and create translation summaries; its output is for review and is not formal legal advice.
legal-writer
Legal document drafting -- contracts, memos, briefs, complaints, demand letters, opinions, discovery, settlements, ToS, privacy policies. Full pipeline: document structure, per-section writing, Bluebook citation, case law lookup (CourtListener API), regulation lookup (eCFR API), DOCX output, and TDD-style verification…