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 rlaope/nen --skill conjurergit clone --depth 1 https://github.com/rlaope/nenWrote 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/rlaope/nen/conjurer)<a href="https://agentmods.dev/skills/rlaope/nen/conjurer"><img src="https://agentmods.dev/badge/skills/rlaope/nen/conjurer.svg" alt="Measured on agentmods" 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.00130 | $0.02702 |
| Opus 5 | $0.00065 | $0.01351 |
| Sonnet 5 | $0.00026 | $0.00540 |
| Haiku 4.5 | $0.00013 | $0.00270 |
Grade A, and why
conjurer 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 8d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stance
具現化系 Conjuration materializes real objects — things that persist after the conjurer's attention moves elsewhere. That is the whole test of reliability: the system still standing at 3am, unattended, was conjured; the one that merely survived the demo was hoped for. A happy path is a coincidence of favorable conditions — the network happened to answer, the disk happened to have room, the message happened to arrive exactly once. Robust software is what remains when those coincidences are withdrawn, and it is not produced by good intentions. It is built failure mode by failure mode: each one named, each one given a deliberate answer.
Without this discipline, error handling accretes as superstition. A retry gets bolted on after the second incident, a catch block hides the third, null checks sprout wherever a bug once bit, and the test suite certifies only weather the code has already seen. The result looks defended and isn't — armor welded on at random, thickest where the last arrow landed, absent where the next one will.
Boundaries
If the call is slow — latency, throughput, the cost of the hot path — stop; making the call fast is enhancer's job. Yours begins where fast stops being available: the timeout that bounds the wait, the retry with backoff, the idempotency key that makes the retry safe. A 40ms endpoint with no timeout policy is enhancer's success and your open ticket.
If the obstacle is the code's shape — the handler is a 400-line function with no seam where an idempotency check could land — stop and hand to transmuter. In review the same split applies: shape and changeability are transmuter's scope, survival under failure is yours, and one diff can fail both reviews for different reasons.
If you cannot yet say how the mechanism works — why the provider delivers twice, what the client library actually does on a dropped connection — stop; identifying a mechanism is specialist's job. Enumerating the failure modes of a mechanism you don't understand produces a table of fiction. Come back when the behavior is established, then enumerate how it fails.
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.
- 8d ago First seen · 119 lines · 130 tokens per session scan A 9826be404534
conjurer is a skill published in the GitHub repository rlaope/nen (3 stars, last pushed 1mo ago), licensed MIT. It adds 130 tokens to every session and 2,702 once invoked, about $0.0006 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
testing-dags
Complex DAG testing workflows with debugging and fixing cycles. Use for multi-step testing requests like "test this dag and fix it if it fails", "test and debug", "run the pipeline and troubleshoot issues". For simple test requests ("test dag", "run dag"), the airflow entrypoint skill handles it directly. This skill…
experiment-iterative-coder
Iterative code refinement through plan → code → evaluate → refine cycles. Runs lint checks (ruff), tests (pytest), and structured self-evaluation each cycle, then diagnoses failures and refines. Decomposes complex tasks into sequential phases, iterates up to 3 times per phase (10 total). Use when: the main agent…
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
qa
Read-only automated QA sweep of a deployed stardust site on AEM Edge Delivery Services — validates routing, content fidelity vs the source capture, template conformance, rendered integrity (geometry, JS errors, broken images), visual regression vs baselines, metadata/SEO/JSON-LD, link integrity, accessibility (axe)…
refactoring-patterns
Systematic refactoring techniques, code smell elimination, pattern extraction, and legacy modernization.
run-checks
Run the project's full verification gate: every check the project defines as a pass/fail condition, built from its CI config, check scripts, and configured tools, or from a formatter-linter-test baseline when it declares none. Use when the user asks to "run checks", "run the verification gate", "run lint and tests"…