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 malekokour/clinpharm-pmx-skills --skill review-line-extensions-routes-formulations-devicesgit clone --depth 1 https://github.com/malekokour/clinpharm-pmx-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/malekokour/clinpharm-pmx-skills/review-line-extensions-routes-formulations-devices)<a href="https://agentmods.dev/skills/malekokour/clinpharm-pmx-skills/review-line-extensions-routes-formulations-devices"><img src="https://agentmods.dev/badge/skills/malekokour/clinpharm-pmx-skills/review-line-extensions-routes-formulations-devices/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/malekokour/clinpharm-pmx-skills/review-line-extensions-routes-formulations-devices"><img src="https://agentmods.dev/badge/skills/malekokour/clinpharm-pmx-skills/review-line-extensions-routes-formulations-devices.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.00136 | $0.02508 |
| Opus 5.5 | $0.00054 | $0.01003 |
| Sonnet 5.5 | $0.00027 | $0.00502 |
| Haiku 4.5 | $0.00014 | $0.00251 |
Grade A, and why
review-line-extensions-routes-formulations-devices 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 1mo 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Line Extensions Routes Formulations Devices
Line extensions - routes, formulations, devices evidence pack — bounded review / prepare / structure workflow for the L3 task Line extensions - routes, formulations, devices (Band B · Post-approval stewardship).
Skills review, reconcile, verify, structure and flag. Qualified humans decide, approve, sign off, submit and act.
Four-box contract
| Box | Content |
|---|---|
| Trigger | Please review the materials for Line extensions - routes, formulations, devices and produce a sourced finding register — do not decide the clinical or regulatory outcome. |
| Input | Primary package for Line extensions - routes, formulations, devices plus the supporting pack in Required inputs |
| Output | Source-linked finding register with denominators; gap / contradiction flags; refuse list |
| Refuses | Decide the outcome of Line extensions - routes, formulations, devices; approve or submit related documents; select or adjust a dose; speak for the sponsor to an agency |
Who this is for
Clinical pharmacology or pharmacometrics practitioners working on Post-approval stewardship who need a repeatable, sourced pass over Line extensions - routes, formulations, devices — not a decision and not a filing.
When to use this skill
- "Please review the materials for Line extensions - routes, formulations, devices and produce a sourced finding register — do not decide the clinical or regulatory outcome."
- "What is evidenced, missing, or inconsistent for: Line extensions - routes, formulations, devices?"
- "Trace every material statement about Line extensions - routes, formulations, devices to a locator."
- "Prepare the review pack for Line extensions - routes, formulations, devices before a meeting or QC cut."
When NOT to use this skill
| Request | Why not this skill | Where it belongs |
|---|---|---|
| Decide clinical significance, dose, or labelling outcome | Human decision | Qualified clinical pharmacologist / labelling owner |
| Approve, sign off, or submit | Human authority | Accountable owner / signatory |
| A different L3 neighbour sharing vocabulary only | Wrong grain or human-owned | the neighbour skill named by the router |
| Decide clinical significance or dose | Wrong grain or human-owned | qualified clinical pharmacologist |
| Run or re-fit a model as the primary ask | Modelling execution | Modelling environment + human modeller |
What ships with it
2 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.
- 1mo ago First seen · 224 lines · 136 tokens per session scan A 48cb7bd5d351
review-line-extensions-routes-formulations-devices is a skill published in the GitHub repository malekokour/clinpharm-pmx-skills (6 stars, last pushed 27d ago), licensed MIT. It adds 136 tokens to every session and 2,508 once invoked, about $0.0005 per session on Opus 5.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-09-03.
Other skills, from other repositories
lab-hardware-cad
Designs custom laboratory hardware as parametric build123d models and exports fabrication artifacts as STEP, STL, and DXF files - microfluidic chips and molds, optomechanical mounts and breadboard adapters, cuvette and microplate holders, tube racks, animal-behavior rigs, and 3D-printed instrument fixtures. Use when a…
opentrons-integration
Authors, reviews, migrates, simulates, and troubleshoots official Opentrons Python Protocol API v2 protocols for Flex and OT-2 robots. Use for robot-specific liquid handling, deck and labware setup, pipettes, modules, runtime parameters, liquid classes, and Opentrons App analysis. Use pylabrobot instead when one…
pylabrobot
Develops and reviews PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Supports PyLabRobot protocols and API questions; keep physical execution behind an explicit operator safety gate.
pybamm
Simulates lithium-ion battery charge, discharge and rest experiments with PyBaMM, records parameter-set provenance, checks mesh and solver sensitivity, and compares predicted voltage curves with measured cycling data. Use for SPM or DFN electrochemical battery modeling, C-rate protocols, voltage cutoffs, parameter…
cmsis-dsp-integration
Use when integrating, configuring, or debugging CMSIS-DSP, ARM math functions, FFT, filters, fixed-point DSP, vector math, or Cortex-M signal processing.
opentrons-integration
Lab automation platform for Flex/OT-2 robots. Write Protocol API v2 protocols, liquid handling, hardware modules (heater-shaker, thermocycler), labware management, for automated pipetting workflows.