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 design-electromagnetic-devicegit 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/design-electromagnetic-device)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/design-electromagnetic-device"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/design-electromagnetic-device/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/design-electromagnetic-device"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/design-electromagnetic-device.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.00086 | $0.04665 |
| Opus 5 | $0.00043 | $0.02332 |
| Sonnet 5 | $0.00017 | $0.00933 |
| Haiku 4.5 | $0.00009 | $0.00466 |
Grade A, and why
design-electromagnetic-device 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 7d 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Electromagnetic Device
Design a practical electromagnetic device by specifying performance requirements, selecting an appropriate topology, calculating design parameters from electromagnetic first principles, analyzing losses and efficiency, and validating the design against physical constraints including thermal limits and material saturation.
When to Use
- Sizing an electromagnet (solenoid or toroidal) for a target field strength, pull force, or holding force
- Selecting motor topology (DC brushed, brushless DC, stepper, induction) and computing torque, speed, and efficiency
- Designing a generator for a specified voltage, current, and frequency output
- Designing a transformer for a given voltage ratio, power rating, and frequency
- Analyzing and minimizing losses: copper (I^2 R), core (hysteresis and eddy current), stray flux
Inputs
- Required: Device type (electromagnet, motor, generator, or transformer)
- Required: Performance requirements (field strength, force, torque, voltage ratio, power, efficiency target)
- Required: Operating conditions (supply voltage and current, frequency, duty cycle, ambient temperature)
- Optional: Preferred core material (silicon steel, ferrite, powdered iron, air core) with B-H data
- Optional: Size and weight constraints
- Optional: Cost or manufacturing constraints
Procedure
Step 1: Specify Device Requirements and Operating Conditions
Define the complete set of design targets before selecting a topology:
-
Primary performance metric: The single most important specification:
- Electromagnet: target B-field (Tesla) at a specified point, or pull force (Newtons) on a specified armature
- Motor: rated torque (N.m) at rated speed (RPM), or power (Watts) at rated speed
- Generator: output voltage (V), current (A), and frequency (Hz) at rated mechanical speed
- Transformer: primary and secondary voltages, power rating (VA), and operating frequency
-
Secondary specifications: Efficiency target (%), maximum temperature rise above ambient (K), duty cycle (continuous, intermittent, or pulsed), physical envelope (maximum diameter, length, weight).
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.
- 7d ago First seen · 300 lines · 86 tokens per session scan A d69c0ed48601
design-electromagnetic-device is a skill published in the GitHub repository pjt222/agent-almanac (32 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 4,665 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-09-03.
Other skills, from other repositories
analytics
Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs…
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".
design-feature
Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
plan-feature
Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling. Persist one severity-ranked, F-numbered report with proposals; never fix or file work. Triggers: "product-audit", "audit the product", "full health check", "are we product-ready", "CTO review".
audit-docs
Audit cross-document coherence: docs ↔ roadmap ↔ code ↔ fix index ↔ issues. Finds drift — features in docs/ not in the roadmap (or vice versa), fix-index entries already merged/closed, broken documentation-map links, dependency cycles, artifacts in the wrong language, naming-convention violations — and reports them…