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 skills add nearform/lastlight --skill security-reviewgit clone --depth 1 https://github.com/nearform/lastlightWrote 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/nearform/lastlight/security-review)<a href="https://agentmods.dev/skills/nearform/lastlight/security-review"><img src="https://agentmods.dev/badge/skills/nearform/lastlight/security-review/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/nearform/lastlight/security-review"><img src="https://agentmods.dev/badge/skills/nearform/lastlight/security-review.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.00059 | $0.02708 |
| Opus 5.5 | $0.00024 | $0.01083 |
| Sonnet 5.5 | $0.00012 | $0.00542 |
| Haiku 4.5 | $0.00006 | $0.00271 |
Grade B, and why
security-review scanned grade B with 3 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
here; new `RUN curl … | sh` / `wget … | bash`; new `--privileged`/`--cap-add`, Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
here; new `RUN curl … | sh` / `wget … | bash`; new `--privileged`/`--cap-add`, Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **Shell exec on attacker-influenced args**: new `execSync`/`exec`/`spawn` where How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review
Review what changed in the repo since the last scan with a security lens,
focused on SDLC concerns that GitHub's built-in scanners (Dependabot, Code
Scanning, Secret Scanning) and Renovate don't cover. File one summary issue
per run, dated, containing a GitHub task list of any findings. Honour
SECURITY.md to suppress accepted risks and false positives.
This is not a general vulnerability scanner. It does not run npm audit
(Dependabot does). It does not run semgrep --config auto over the whole tree
(Code Scanning does). It looks at the diff since the prior scan and surfaces what
humans introduced — CI hardening, auth changes, secret handling in new code,
supply-chain churn.
The summary issue's structure is the machine-parsed contract a maintainer's
later comment is processed against (the security-feedback skill). It is defined
in references/issue-format.md — follow it
exactly when composing the issue (§9).
Context
context.repo—owner/nameto scancontext.issueDir— directory for the run summary file (e.g..lastlight/security-<date>)
Procedure
1. Clone, find the prior-scan anchor, read SECURITY.md
- Clone the target repo via
github_clone_repo. - Prior scan anchor. Query issues labelled
security-scan(open OR closed), newest first. Read the latest one's body for the<!-- lastlight-security-scan-ts: ... -->comment and use that ISO-8601 timestamp aspriorScanTs. No prior scan issue →priorScanTs = now - 30 days(bootstrap floor — keeps the first run finite). - Read
SECURITY.mdat the repo root (if present): per-tool severity floors (defaultmedium; skiplow/info), the accepted-risks table, and the false-positives table (both keyed by finding fingerprint).
1.5. Compute the changeset
Most weeks the diff is dominated by Renovate/Dependabot churn — strip it so the scope is what humans wrote.
git log --since="${priorScanTs}" --pretty=format:'%H|%an|%ae|%s'.- Drop a commit when either: author email matches
*[bot]@users.noreply.github.comand name isdependabot[bot]/renovate[bot]/github-actions[bot]; OR the subject starts withchore(deps),chore(deps-dev),build(deps),build(deps-dev),fix(deps). - Accumulate changed files from the surviving commits
(
git diff-tree --no-commit-id --name-only -r ${sha}) into a dedupedchangedFilesset. - Drop entries that are only lockfiles (
package-lock.json,pnpm-lock.yaml,yarn.lock,bun.lockb,Gemfile.lock,poetry.lock,uv.lock,Cargo.lock,composer.lock) — catches lockfile changes mixed into human commits. - Build
commitsReviewed= surviving commits as{ shortSha, subject }(used in the scope note).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 208 lines · 59 tokens per session scan B b90c91090e20
security-review is a skill published in the GitHub repository nearform/lastlight (40 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 2,708 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 3 findings (downloads and executes remote code, makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
orca
Use when the user asks to run an Orca flow (e.g. "use orca to implement …"), or when delegating a well-defined implementation task to Orca's autonomous multi-agent flow — a headless plan-code-review CLI to hand a coding task to instead of implementing it yourself.
Codex
Guides operator-owned delegation to Codex when the task fits a bounded coding lane, review pass, or worktree-isolated implementation track.
example-skill
Counts lines, words, and bytes in a text file using the bundled count.sh script. Use when asked to count/measure a file's size in these terms.
open-code-review
Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…
rubber-duck
Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…
shap
Model interpretability and explainability using SHAP (SHapley Additive exPlanations). Use this skill when explaining machine learning model predictions, computing feature importance, generating SHAP plots (waterfall, beeswarm, bar, scatter, force, heatmap), debugging models, analyzing model bias or fairness, comparing…