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 jack20040828/kangmaojian-skills --skill review-opinion-deliverygit clone --depth 1 https://github.com/jack20040828/kangmaojian-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/jack20040828/kangmaojian-skills/review-opinion-delivery)<a href="https://agentmods.dev/skills/jack20040828/kangmaojian-skills/review-opinion-delivery"><img src="https://agentmods.dev/badge/skills/jack20040828/kangmaojian-skills/review-opinion-delivery/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/jack20040828/kangmaojian-skills/review-opinion-delivery"><img src="https://agentmods.dev/badge/skills/jack20040828/kangmaojian-skills/review-opinion-delivery.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.00150 | $0.01234 |
| Opus 5 | $0.00075 | $0.00617 |
| Sonnet 5 | $0.00030 | $0.00247 |
| Haiku 4.5 | $0.00015 | $0.00123 |
Grade A, and why
review-opinion-delivery 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 12d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
施工图审查意见整理交付
Package opinions already made by the reviewer into a faithful, evidence-linked Word deliverable. Keep this workflow separate from technical drawing review.
Non-Negotiable Boundary
- Treat the reviewer's latest confirmed DOCX as the highest content and style authority. Preserve its approved wording, item scope, certainty, regulation text, item consolidation, and mandatory/suggested status.
- Do not add, remove, strengthen, weaken, merge, split, or infer a technical conclusion without explicit reviewer approval.
- Use drawings only to locate marks and verify transcription. Do not derive new issues from them.
- Preserve
无only when it is reviewer-approved or explicitly confirmed as an internal contradiction, missing name/index, or design-expression issue that does not assert an external threshold. An unreviewed placeholder无blocks delivery; regulation research, completion, and conclusion reclassification require a separately authorizedbuilding-reviewphase. - Correct obvious typos, punctuation errors, and deterministic opinion-type aliases; record the before/after/reason in
edit_log.csv. - If a correction has two plausible results or could change
必须修改/建议修改, technical meaning, applicability, or responsibility, mark it需确认and stop delivery. - Every opinion type must resolve to one of the 12 canonical values in
references/opinion-types.json; invalid or unresolved values are a hard failure. - Record material source conflicts as
需确认; do not silently correct professional substance.
Read references/scope-boundary.md before editing any opinion.
Required Workflow
- Create a workspace with
scripts/create_delivery_workspace.py. For an existing project, pass--root <project>\03_审图过程. - Preserve every original under
source/. Never overwrite a source file. - After the source set is stable, run
scripts/snapshot_source_integrity.py <workspace>. - Build the v1.2
delivery_manifest.jsonwith immutableitem_id, displayitem_no, approved fields, provenance, evidence strategy, and zero or moreevidence_images. Distinguish reviewer-approved regulation无from an unreviewed placeholder in the verification record. Fillverification_log.csvandedit_log.csv. - For marked DWG evidence, plot a working copy to PDF and crop only from rendered PDF pages. Never place CAD/T20 interface screenshots in the formal Word.
- Run
scripts/normalize_opinion_types.py <workspace>and thenscripts/validate_delivery_package.py <workspace>before editing or generating the final Word. Deterministic corrections are mandatory; unresolved types must block delivery. - If a reviewer-approved DOCX exists, use the newest one as the base and make only approved local edits. Use
scripts/generate_delivery_report.pyonly when no base DOCX exists. - Run
scripts/validate_docx_content.py; formal Word text must not expose notes, note IDs, 得到大脑, evidence-source labels, PDF page traces, mark numbers, crop coordinates, or red-box explanations. Export to PDF, render every page, inspect every page, then runscripts/validate_report_qa.py. - Deliver only after both content and visual gates pass. Copy the final DOCX to
<project>\04_审图成果; do not make scripts guess the project root.
What ships with it
26 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.
- agents/openai.yaml 457 B
- evals/regression-cases.json 3.4 KB
- evals/routing-cases.json 4.0 KB
- evals/run_regression_checks.py 9.6 KB runs code
- evals/run_v12_regression_checks.py 19 KB runs code
- references/delivery-style.md 5.1 KB
- references/gotchas.md 4.0 KB
- references/opinion-types.json 885 B
- references/qa-checklist.md 3.2 KB
- references/runtime-requirements.md 825 B
- references/scope-boundary.md 3.5 KB
- references/screenshot-standard.md 2.4 KB
- references/workflow.md 5.9 KB
- scripts/compare_reviewer_docx.py 23 KB runs code
- scripts/compose_evidence_cards.py 5.4 KB runs code
- scripts/create_delivery_workspace.py 3.6 KB runs code
- scripts/export_docx_to_pdf.ps1 1.0 KB runs code
- scripts/generate_delivery_report.py 7.4 KB runs code
- scripts/normalize_opinion_types.py 4.0 KB runs code
- scripts/opinion_types.py 2.0 KB runs code
- scripts/render_pdf_pages.py 2.7 KB runs code
- scripts/snapshot_source_integrity.py 2.7 KB runs code
- scripts/validate_delivery_package.py 15 KB runs code
- scripts/validate_docx_content.py 7.7 KB runs code
- scripts/validate_eval_assets.py 3.7 KB runs code
- scripts/validate_report_qa.py 2.6 KB runs code
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.
- 12d ago First seen · 57 lines · 150 tokens per session scan A 93602d9a9615
review-opinion-delivery is a skill published in the GitHub repository jack20040828/kangmaojian-skills (3 stars, last pushed 19d ago), licensed MIT. It adds 150 tokens to every session and 1,234 once invoked, about $0.0007 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-31.
Other skills, from other repositories
code-to-diagram
Analyze codebases and automatically generate architecture diagrams, flowcharts, and org charts. Uses AST parsing to map import dependencies for Python, JS/TS, Go, and Java, outputting Mermaid or SVG files. Triggered when users ask to visualize code architecture, understand dependencies, draw a flowchart, or create a…
csv-to-sif
Export a project's FF&E product-library CSV as dealer-system SIF. Use to produce a .sif schedule; use sif-to-csv for the reverse direction.
epd-parser
Extract GWP, life-cycle stages, certifications, and impact metrics from an EPD PDF. Use when given a declaration to parse; not to find or compare EPDs.
product-data-cleanup
Clean a local FF&E CSV schedule by normalizing casing, dimensions, units, language, materials, and formatting. Use when asked to clean, fix, or standardize product data.
product-data-import
Generate a formatted FF&E specification schedule from notes, CSV, or pasted lists and optionally save it to the project's 33-column CSV library. Use when asked to import products or build a schedule.
product-spec-pdf-parser
Extract structured FF&E specs from PDF price books, fact sheets, or spec sheets into a schedule. Use for product PDFs; not web URLs or EPDs.