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 agentmods add skills/lerianstudio/ring/engineering-promptsnpx skills add LerianStudio/ring --skill engineering-promptsgit clone --depth 1 https://github.com/LerianStudio/ringWrote 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/lerianstudio/ring/engineering-prompts)<a href="https://agentmods.dev/skills/lerianstudio/ring/engineering-prompts"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/engineering-prompts.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.00074 | $0.01083 |
| Opus 5 | $0.00037 | $0.00541 |
| Sonnet 5 | $0.00015 | $0.00217 |
| Haiku 4.5 | $0.00007 | $0.00108 |
Grade B, and why
ring:engineering-prompts scanned grade B with 1 finding 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 6d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
1. **Display Prompt**: Show complete prompt text in formatted code block How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Prompts
When to use
- Crafting new prompts for LLM-based systems or AI assistants
- Optimizing existing prompts that underperform or produce inconsistent results
- Selecting appropriate prompting techniques for a specific use case
- Structuring complex multi-step reasoning prompts
Skip when
- The prompt is trivial and already producing good results
- The task is a direct code change, not prompt creation
- You need to execute the task described in the prompt rather than create a prompt for it
Scope Boundaries
THIS SKILL ONLY GENERATES PROMPTS. IT NEVER:
- Proactively explores, modifies, or debugs any files in the codebase
- Attempts to fix, debug, or improve code in the project
- Performs the task described in the user's input
Allowed reads: Files the user explicitly references as input context, and docs/prompts/ for saving output.
THE INPUT IS A DESCRIPTION OF WHAT THE PROMPT SHOULD DO, NOT A TASK TO PERFORM.
Example: Help debug React performance issues means:
- CREATE a prompt that helps users debug React performance issues
- DO NOT actually debug any React code
Process
Phase 1: Input Analysis
- Parse Input: Analyze the provided description or file content
- Identify Use Case: Determine the intended application and requirements
- Select Techniques: Choose appropriate prompting patterns and methods
Phase 2: Prompt Construction
- Structure Design: Create clear prompt architecture using proven patterns
- Technique Application: Apply selected prompting techniques (few-shot, chain-of-thought, etc.)
- Constraint Setting: Define boundaries and output format specifications
- Validation: Ensure prompt follows best practices and guidelines
Phase 3: Documentation & Delivery
- Display Prompt: Show complete prompt text in formatted code block
- Implementation Notes: Explain techniques used and design rationale
- Usage Guidelines: Provide clear instructions for implementation
- Performance Tips: Include optimization suggestions and best practices
- Save Output: Save the generated prompt to
docs/prompts/directory (create if needed)
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.
- 6d ago First seen · 146 lines · 74 tokens per session scan B e6de2537ae3e
ring:engineering-prompts is a skill published in the GitHub repository LerianStudio/ring (211 stars, last pushed 17d ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,083 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
mutation-test
Mutation testing with two engines. Uses the project's NATIVE mutation runner (StrykerJS / Infection / mutmut / PIT / cargo-mutants) when one is configured — installing it on explicit consent when it is not — for a reproducible, comparable score; and an LLM-guided engine for the mutation classes native mutators cannot…
infra-audit
Server / infrastructure security audit of LIVE hosts over SSH (12 dimensions IS1-IS12: SSH hardening, accounts, network exposure, TLS, firewall, patch posture, logging, web services, Docker, databases, filesystem, host secrets). Deterministic collector + parallel LLM analysts; dual-vantage (internal SSH + external via…
kanso-prompting
Use when rewriting, sharpening, or producing a prompt for Claude or another current frontier model. Sets standing rules for getting better LLM output through better prompts. Loaded by /kanso-task; not directly invoked by the user.
prompt-engineering
Use when writing prompts for AI tools, optimizing agent system prompts, or designing AI-readable instructions. Covers prompt structure, meta-prompting, chain-of-thought, and tool-specific optimization.
execution/data-executor
Internal: Data Executor. Implements ETL, analytics, backfills, data quality, reconciliation, and data pipeline changes. Write evidence on completion.
execution/ml-executor
Internal: ML Executor. Implements ML models, training pipelines, inference code, data processing. Read spec and segment. Write evidence on completion.