Borrowing it
Nothing to install: this file belongs to hatyibei/shingan. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hatyibei/shingan/main/.claude/commands/add-security-rule-support-for-langgraph-js.mdgit clone --depth 1 https://github.com/hatyibei/shinganWrote 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/commands/hatyibei/shingan/add-security-rule-support-for-langgraph-js)<a href="https://agentmods.dev/commands/hatyibei/shingan/add-security-rule-support-for-langgraph-js"><img src="https://agentmods.dev/badge/commands/hatyibei/shingan/add-security-rule-support-for-langgraph-js/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/commands/hatyibei/shingan/add-security-rule-support-for-langgraph-js"><img src="https://agentmods.dev/badge/commands/hatyibei/shingan/add-security-rule-support-for-langgraph-js.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.00025 | $0.00362 |
| Opus 5.5 | $0.00010 | $0.00145 |
| Sonnet 5.5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
add-security-rule-support-for-langgraph-js 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 1mo 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-security-rule-support-for-langgraph-js
Use this workflow when working on add-security-rule-support-for-langgraph-js in shingan.
Goal
Implements extraction logic for a new security rule in the langgraph-js parser shim, adds corresponding test fixtures (safe and vuln), and updates Go tests to verify rule firing and regression.
Common Files
infrastructure/parser/shims/export_langgraphjs_server.mjstestdata/langgraphjs/*_safe.tstestdata/langgraphjs/*_vuln.tsinfrastructure/parser/langgraphjs_test.go
Suggested Sequence
- Understand the current state and failure mode before editing.
- Make the smallest coherent change that satisfies the workflow goal.
- Run the most relevant verification for touched files.
- Summarize what changed and what still needs review.
Typical Commit Signals
- Update infrastructure/parser/shims/export_langgraphjs_server.mjs to extract new config or schema for the rule.
- Add or update test fixtures in testdata/langgraphjs/ (e.g., *_safe.ts and *_vuln.ts) to exercise both safe and vulnerable cases.
- Update or create Go test assertions in infrastructure/parser/langgraphjs_test.go to check that the rule fires or does not fire as expected.
- Run regression tests to ensure no unintended changes to existing fixtures.
Notes
- Treat this as a scaffold, not a hard-coded script.
- Update the command if the workflow evolves materially.
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.
- 1mo ago First seen · 39 lines · 25 tokens per session scan A 5f1121b2199f
add-security-rule-support-for-langgraph-js is a command published in the GitHub repository hatyibei/shingan (2 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 362 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
analyze
Full GoSQLX analysis of a SQL string or .sql file (validity, metadata, security, lint, formatting).
format
Format a SQL string or .sql file with GoSQLX.
security
Scan a SQL string, .sql file, or SQL-building source file for injection risks with GoSQLX.
orchestrator
Bind this session as Ledger Orchestrator.
bmad-review-edge-case-hunter
Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.
bmad-code-review
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code".