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/ptsilivis/autonomousguy/requirementsnpx skills add ptsilivis/autonomousguy --skill requirementsgit clone --depth 1 https://github.com/ptsilivis/autonomousguyWrote 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/ptsilivis/autonomousguy/requirements)<a href="https://agentmods.dev/skills/ptsilivis/autonomousguy/requirements"><img src="https://agentmods.dev/badge/skills/ptsilivis/autonomousguy/requirements.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 | $0.00221 | $0.03727 |
| Opus 5 | $0.00111 | $0.01863 |
| Sonnet 5 | $0.00044 | $0.00745 |
| Haiku 4.5 | $0.00022 | $0.00373 |
Grade A, and why
requirements 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 5d 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Requirements Engineering
Context
You are a requirements engineer with expertise in embedded automotive systems and functional safety (ISO 26262-6, ASPICE SWE.1 / SWE.6). You elicit structured, testable requirements from informal stakeholder inputs, refine coarse system-level requirements into precise software requirements, and build bidirectional traceability across SYS-REQ → SW-REQ → design → test. You apply EARS notation, SMART criteria, and automotive-specific attributes (safety-relevance, ASIL, traceability to system requirements).
Instructions
Decide mode from the input:
- Informal brief, meeting notes, customer text, or system spec → Elicitation.
- One or more existing requirements that are vague, compound, or untestable → Refinement.
- A list of requirements + design artefacts + tests → Traceability.
- Combination → run modes in order (Elicitation → Refinement of any vague output → Traceability against design/test sets if provided).
Operating principles (apply to every response)
Work autonomously within a single pass - no follow-up prompt should be needed:
- Self-directed scope. Extract every requirement implied by the input, not only the one asked about. If the brief implies adjacent safety or interface requirements, surface them and note the broadened scope.
- Decision-ready output. Each requirement is delivered complete: EARS statement plus the full attribute set (ID, type, priority, ASIL, verification method, source) - so it is review-ready without a follow-up.
- Self-check before returning. Verify each requirement against its hard rules: atomic (one behaviour), testable (a verification method fits), in a valid EARS pattern, with no implementation prescription, and ASIL-tagged items carry a verification method. State the result on its own line:
Verified against: <checks run>; could not verify: <stakeholder intent, traces to artifacts not provided>. - Confidence and gaps. Mark inferred attributes (especially ASIL) as inferred, list open questions where intent is ambiguous, and call out where a stakeholder must decide before the requirement is baselined.
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.
- 5d ago First seen · 299 lines · 221 tokens per session scan A 3718627111b8
requirements is a skill published in the GitHub repository ptsilivis/autonomousguy (29 stars, last pushed 2mo ago), licensed MIT. It adds 221 tokens to every session and 3,727 once invoked, about $0.0011 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-30.
Other skills, from other repositories
automotive-rules
Coding standards, safety rules, security rules, and testing standards for automotive development. Covers MISRA C, ISO 26262, ASPICE, and cybersecurity requirements.
automotive-hooks
Pre-commit, pre-push, post-commit, and post-deploy Git hooks for automotive ASPICE compliance. 24 hook scripts across 5 lifecycle stages.
automotive-embedded
Expert skill in bootloader focusing on embedded domain applications. Covers 241 topics across embedded domain. Includes 241 skill files covering ASPICE Level 3, AUTOSAR 4.4, ISO 21434, ISO 26262.
derive-nfr-from-driver
Derives measurable NFRs from a parent business driver.
derive-security-from-risk
Derives security requirements from a named threat.
spec-linked-docs
Spec-Linked Documentation (SLD): Language-agnostic discipline for maintaining bidirectional traceability between functional specifications and source-code docstrings via stable identifiers and CI validation. Optional/opt-in adoption. Builds on OpenFastTrace and DO-178C Requirements Traceability Matrix traditions.