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 Sliky1/lagrangian-skills --skill v0.5.0git clone --depth 1 https://github.com/Sliky1/lagrangian-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/sliky1/lagrangian-skills/v0.5.0)<a href="https://agentmods.dev/skills/sliky1/lagrangian-skills/v0.5.0"><img src="https://agentmods.dev/badge/skills/sliky1/lagrangian-skills/v0.5.0/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/sliky1/lagrangian-skills/v0.5.0"><img src="https://agentmods.dev/badge/skills/sliky1/lagrangian-skills/v0.5.0.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.00080 | $0.00704 |
| Opus 5 | $0.00040 | $0.00352 |
| Sonnet 5 | $0.00016 | $0.00141 |
| Haiku 4.5 | $0.00008 | $0.00070 |
Grade A, and why
lagrangian-core 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 11d 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
Lagrangian Core Skill — v0.5.0
能力边界
支持: 凸QP | 光滑NLP | 非凸NLP | 分布式ADMM | Safe RL | 多目标 协同: 检测贝叶斯/统计成分→HALT并建议调用对应Skill 不支持: 纯贝叶斯 | 纯统计检验 | MIP
输出模式: MINIMAL | STANDARD(默认) | VERBOSE
Step -1 — 预检 (4项并行)
- 变量类型 2. 约束可行性 3. 问题规模 4. 量纲一致性 HALT条件 → 立即停止，输出错误码
Step 0 — 澄清
模糊点→单轮确认；贝叶斯信号→HALT "请调用贝叶斯Skill"
Step 3 — 稀疏JSON通道
{"step":3,"type":"augmented_lagrangian",
"formula":"L_ρ=f(x)+Σλ·h(x)+Σμ·g(x)+ρ/2·||h||²",
"multipliers":{"lambda":[0.0],"mu":[0.0]},
"penalty":{"rho_init":1.0,"update_rule":"×1.5 if ||h||>tol"}}
Step 5 — 求解路由
safe_rl+adversarial → cos_thresh=0.15, window=15
multi_obj+adversarial → max_repair=3, repair_freq=8
non_convex+adversarial → ALM(n_starts=10, uniform_random)
non_convex+normal → ALM(n_starts=10, warm_start=cache)
convex_qp/smooth_nlp → standard_solver
distributed → ADMM
Step 6 — 影子价格
只输出活跃约束(影子价格>0)
Step 7 — 输出
STANDARD: 最优解(一行) → 约束状态(仅活跃) → 关键瓶颈(一句) VERBOSE: STANDARD + Steps 3-6 JSON
失败处理
{"status":"FAILED","error_code":"INFEASIBLE|BAD_PARAMS|AMBIGUOUS|SOLVER_FAIL",
"reason":"<一行>","recovery":"<修复建议>"}
Forbidden Behaviors
❌ Steps 1-6输出自然语言 | ❌ Step 7输出JSON ❌ 语言边界直接HALT | ❌ 失败后输出散文 ❌ FIX-16: cos_thresh>0.20或window<15
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.
- 11d ago First seen · 65 lines · 80 tokens per session scan A aefd113f60be
lagrangian-core is a skill published in the GitHub repository Sliky1/lagrangian-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 80 tokens to every session and 704 once invoked, about $0.0004 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
audit-reproducibility
Enforce the replication-protocol.md rule by cross-checking numeric claims in a manuscript against the actual R / Stata / Python outputs. Report PASS/FAIL per claim against tolerance thresholds. Use before submission and before releasing a replication package.
review-paper
Comprehensive manuscript review with three modes: single-pass (default), --adversarial critic-fixer loop, and --peer [journal] simulated peer-review pipeline (editor + 2 dispositioned referees + editorial decision, calibrated to a target journal). R&R continuation via --peer --r2/--r3; hostile-editor stress test via…
grant-proposal
Scaffold a research grant proposal (NSF, NIH, ERC, or foundation) by composing existing primitives — pulls identification strategy from an /interview-me spec, delegates the data-management plan to /data-management-plan and the facilities statement to /capture-environment, and emits a funder-requirements checklist. Use…
preregister
Draft a structured preregistration document (OSF, AsPredicted, or AEA RCT Registry style) from a research spec or free-form study description. Output is a Markdown file with hypotheses, design, sampling plan, analysis plan, exclusions, and inference criteria — annotated with MUST / SHOULD / MAY clarity flags. Use when…
capture-environment
Snapshot the computational environment for a replication package — detects the analysis stack (R / Stata / Python) and emits the right lockfiles (renv.lock + sessionInfo.txt, requirements.txt / environment.yml / uv.lock, Stata version + ado package list), records seeds and RNG kind, optionally writes a pinning…
data-management-plan
Draft a funder-compliant Data Management Plan (NSF DMP, NIH DMS Policy 2023, ERC, Horizon Europe) by composing the confidential-data and environment-capture primitives. Sections cover data description, formats/metadata, storage/backup, access/sharing, preservation/archiving, and roles. Use when user says "data…