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 pjt222/agent-almanac --skill develop-gc-methodgit clone --depth 1 https://github.com/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/develop-gc-method)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/develop-gc-method"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/develop-gc-method/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/pjt222/agent-almanac/develop-gc-method"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/develop-gc-method.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.00045 | $0.02798 |
| Opus 5.5 | $0.00018 | $0.01119 |
| Sonnet 5.5 | $0.00009 | $0.00560 |
| Haiku 4.5 | $0.00005 | $0.00280 |
Grade A, and why
develop-gc-method 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop a GC Method
Systematic development of a gas chromatography method covering column selection, temperature program optimization, carrier gas and detector choice, and initial performance verification for volatile and semi-volatile analytes.
When to Use
- Starting a new GC analysis for volatile or semi-volatile compounds
- Adapting a published method to a different instrument or matrix
- Replacing an existing method that no longer meets performance requirements
- Developing a method for compounds with known boiling points and polarities
- Transitioning from a packed-column method to a capillary method
Inputs
Required
- Target analytes: List of compounds with CAS numbers, molecular weights, and boiling points
- Sample matrix: Description of the sample type (e.g., air, water extract, solvent solution, biological fluid)
- Detection limits: Required LOD/LOQ for each analyte
Optional
- Reference method: Published method (EPA, ASTM, pharmacopeial) to use as a starting point
- Available columns: Inventory of columns already on hand
- Instrument configuration: GC model, available detectors, autosampler type
- Throughput requirements: Maximum acceptable run time per sample
- Regulatory framework: GLP, GMP, EPA, or other compliance context
Procedure
Step 1: Define Analytical Objectives
- List all target analytes with their physical properties (boiling point, polarity, molecular weight).
- Identify the sample matrix and any expected interferents or co-extractives.
- Specify required detection limits, quantitation range, and acceptable resolution between critical pairs.
- Determine whether the method must meet a regulatory standard (EPA 8260, USP, etc.).
- Document throughput needs: maximum run time, injection volume, sample preparation constraints.
Got: A written specification listing analytes, matrix, detection limits, resolution requirements, and any regulatory or throughput constraints.
If fail: If analyte volatility data is unavailable, estimate boiling points from structural analogs or use a scouting run on a mid-polarity column to establish elution order.
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 · 194 lines · 45 tokens per session scan A f906f366026d
develop-gc-method is a skill published in the GitHub repository pjt222/agent-almanac (42 stars, last pushed 5d ago), licensed MIT. It adds 45 tokens to every session and 2,798 once invoked, about $0.0002 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
astro-dso-doc
Bootstraps a deep-sky object (DSO) astrophotography project from raw acquisition frames (own rig, not a smart telescope), AND generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), and a ready-to-paste PixInsight project Description…
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
execute-phase
Step executor for units whose triage (unit-lane) decided which steps the unit needs. Implements one triaged step (or all remaining steps), with frozen acceptance, step-local gates, commits, red-gate repair, and diff-size guard. BREAKING: replaced PLAN.md/TASKS.md/progress.md/ACCEPTANCE.md with the unit doc's Tasks…
fold-findings
Repair persisted fix-now findings in compatible atomic batches: root-cause fixes, green gate, commit/push, and per-row folded: yes updates. Never reclassify or substitute backlog notes. Triggers: "fold-findings", "fix the review findings", "repair audit blockers".
init-workspace
Adapt the workflow scaffold to a new repository or add only missing substrate blocks to an existing install. Every install, hook, and overwrite needs explicit consent. Triggers: "init-workspace", "set up agentic workflow", "upgrade workflow scaffold".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling; it owns the repo-wide bug hunt, security research, and broken-version investigation (scoped and budgeted per dimension, as distinct from review-change's change-scoped review). Persist one severity-ranked, F-numbered report with…