Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rajdeepratan/SlashForgenpx agentmods add skills/rajdeepratan/slashforge/add-guide-fileWrote 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/rajdeepratan/slashforge/add-guide-file)<a href="https://agentmods.dev/skills/rajdeepratan/slashforge/add-guide-file"><img src="https://agentmods.dev/badge/skills/rajdeepratan/slashforge/add-guide-file/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/rajdeepratan/slashforge/add-guide-file"><img src="https://agentmods.dev/badge/skills/rajdeepratan/slashforge/add-guide-file.svg" alt="Reviewed on agentmods" width="80" 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.00040 | $0.00601 |
| Opus 5.5 | $0.00016 | $0.00240 |
| Sonnet 5.5 | $0.00008 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
add-guide-file 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.
What it actually says
Add a guide file
A "guide" is a templates/slashforge-*.md reference that is installed next to the
commands and read by agents at runtime (e.g. slashforge-workflow-verify.md).
This recipe adds one and wires it so the installer actually ships it.
Before starting
Read .claude/rules/templates.md (authoring rules) and .claude/rules/cli.md
(installer conventions).
Steps
- Create the file at
templates/slashforge-<name>.md. Start with YAML frontmatter (name,description) and keep the body ≤ 200 lines. If it would run longer, split it and link a sibling guide. - Use per-host target blocks for any host-specific wording — balanced
<!--target:claude-->…<!--/target-->/<!--target:agents-->…<!--/target-->. Valid names:claude,agents,cursor,codex,neutral. - Register it in the installer. Add the filename to the
GUIDE_FILESarray inbin/install.js(keep it near related guides). An unregistered guide is never installed. - Reference it from whatever guide or command loads it (e.g. a
workflow.md"companion files" list). A guide nothing points to is dead weight. - Run the tests —
npm test. Frontmatter, line-limit, and target-block checks run here. - Regenerate the Claude render snapshot (the pinned-render test will otherwise fail, by design):
Review the diff: the new guide should appear, and nothing unrelated should change.node scripts/snapshot-claude-render.js git diff test/fixtures/claude-render - Update
CHANGELOG.mdunder## [Unreleased]describing the new guide.
Verify
- File is ≤ 200 lines with valid frontmatter
- Every
<!--target:x-->has a matching<!--/target-->; all target names are valid - Filename added to
GUIDE_FILESinbin/install.js - At least one existing guide/command references the new file
-
npm testpasses -
test/fixtures/claude-renderregenerated and the diff reviewed -
CHANGELOG.mdupdated
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 · 43 lines · 40 tokens per session scan A c1be026be8c9
add-guide-file is a skill published in the GitHub repository rajdeepratan/SlashForge (5 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 601 once invoked, about $0.0002 per session on Opus 5.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-10-09.
Other skills, from other repositories
openclaw-github-repo-commander
7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis.
Git Workflow
Use this skill when you want a clean Git history (easy reviews, easy rollbacks) and consistent PR hygiene—especially when an agent is helping you make changes across multiple files.
verify-change
A change-checking skill that reviews code differences and checks whether related documentation, tests, and records were updated.
verify-module
A module-checking skill that scans a project’s folders, code, and documentation. It expects each module to include a README.md and DESIGN.md, which explain how the module is used and why it was designed that way.
verify-quality
A code-quality checker that measures complexity, size, naming, and common code smells. It reports problems such as duplicated code, unused code, and overly long functions.
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.