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/fjpulidop/specrails-core/testnpx skills add fjpulidop/specrails-core --skill testgit clone --depth 1 https://github.com/fjpulidop/specrails-coreWrote 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/fjpulidop/specrails-core/test)<a href="https://agentmods.dev/skills/fjpulidop/specrails-core/test"><img src="https://agentmods.dev/badge/skills/fjpulidop/specrails-core/test.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.00043 | $0.00488 |
| Opus 5 | $0.00022 | $0.00244 |
| Sonnet 5 | $0.00009 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
test 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 4d 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.
What it actually says
Test Generator
Generate comprehensive tests for implementation files using the sr:test-writer agent.
Input: $ARGUMENTS
- File paths:
/specrails:test src/api/users.ts src/utils/auth.ts - Glob:
/specrails:test "src/**/*.ts" - Empty:
/specrails:test— tests all files changed since last commit
Step 1: Determine target files
If $ARGUMENTS is provided:
- Parse the arguments as file paths or a glob pattern
- Expand any globs to a list of files
- Validate each file exists
If $ARGUMENTS is empty:
git diff --name-only HEAD~1 HEAD 2>/dev/null || git diff --name-only --cached
- Use the list of changed files as the target
- Filter out test files (.test., .spec., _test.go, spec/**)
- Filter out non-code files (*.md, *.json, *.yaml, *.lock)
If no files remain after filtering: print "No implementation files to test." and stop.
Step 2: Confirm scope
Print the list of files that will be tested:
Generating tests for:
src/api/users.ts
src/utils/auth.ts
Launch sr:test-writer? [Y/n]
Step 3: Launch sr:test-writer
Launch the sr:test-writer agent (subagent_type: sr:test-writer, foreground).
Provide this context in the prompt:
IMPLEMENTED_FILES_LIST:
<list of target files, one per line>
TASK_DESCRIPTION:
Generate comprehensive tests for the files listed above. Target >80% coverage. Follow existing test patterns in this project.
Wait for the agent to complete.
Step 4: Report results
Display the TEST_WRITER_STATUS from the agent output and summarize:
- Which test files were written
- Which files were skipped and why
- Any issues encountered
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.
- 4d ago First seen · 78 lines · 43 tokens per session scan A f8c1c1b3634c
test is a skill published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 488 once invoked, about $0.0002 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
knowledge-base
Create and maintain a Markdown knowledge base that any AI agent can read, search, and update. Use when the user wants to start a knowledge base, add or update notes, organize docs/notes for an agent or LLM to consume, build an index of notes, or run a cleanup/maintenance pass on an existing MD knowledge base. Triggers…
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
taiyi-integration
TaiyiForge 第9阶段 — 闭环归档,CHANGELOG.md。四端通用。.
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约,产出 UI-DESIGN.md。四端通用。.
taiyi-evolve
TaiyiForge 辅助 — 实现后架构与文档同步(architecture-sync)。OpenCode / Claude / Codex / Cursor 通用。.