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 forefy/.context --skill broken-access-controlgit clone --depth 1 https://github.com/forefy/.contextWrote 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/forefy/.context/broken-access-control)<a href="https://agentmods.dev/skills/forefy/.context/broken-access-control"><img src="https://agentmods.dev/badge/skills/forefy/.context/broken-access-control/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/forefy/.context/broken-access-control"><img src="https://agentmods.dev/badge/skills/forefy/.context/broken-access-control.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.02523 |
| Opus 5.5 | $0.00012 | $0.01009 |
| Sonnet 5.5 | $0.00006 | $0.00505 |
| Haiku 4.5 | $0.00003 | $0.00252 |
Grade A, and why
broken-access-control scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sk -o /dev/null -w '%{http_code} %{size_download}b\n' \ How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contents
- Scope & authorization
- Methodology (baseline, identity-swap, numeric IDOR)
- Runnable snippets
- IDOR numeric-parameter wordlist
- Thresholds (carry these exactly)
- Output
Scope & authorization
Only run against an application the user owns or is contractually engaged to test. This is an ACTIVE, aggressive check: it re-sends real requests to the target under different identities and with mutated object-ids, so it creates traffic, may read or touch other users' data, and can trip rate-limits or alerts. Use a staging environment or a maintenance window where you can, keep the identities and object-ids to accounts you control, and stop if you start returning data that clearly belongs to real third parties. If scope is unclear, ask before replaying.
Two things must exist before you start:
- A capture of the target's traffic taken as a privileged / higher-role user (from a proxy, HAR export, or your own request log). Each captured request gives you the method, URL, headers, query params, cookies, and body.
- At least one second identity to replay under - a lower-privileged user's session, and/or the unauthenticated (no-token, no-cookie) state. An identity is either a cookie (
name=value) or a bearer token (Authorization: Bearer ...).
This skill covers authorization replay and numeric IDOR on already-captured requests. It does not fuzz for hidden endpoints, mutate non-numeric/UUID object references, or bypass auth at the token layer (JWT tampering, session fixation) - note those as unrun if the target warrants a deeper pass.
Methodology (run in order; each step is a check with a result state)
-
Inventory the capture. From the privileged capture, list each request as its parts: method, full URL, headers, query params, cookies, body. These are the units you replay; you never craft new endpoints, only re-send captured ones under new conditions.
-
Baseline each request as the privileged user. Re-send it exactly as captured and record
status_codeand response body length. This is the reference every swapped-identity and mutated-id response is compared against, and it confirms the request still works before you draw conclusions from a difference.
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 · 157 lines · 31 tokens per session scan A 82d22cb445de
broken-access-control is a skill published in the GitHub repository forefy/.context (153 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 2,523 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
fizz
Generate Echidna/Medusa-compatible Solidity fuzz suites from Foundry or Hardhat projects. Trigger on "fizz", "generate fuzz suite", "build fuzz harness", "stateful fuzzing", "fuzzing harness", "property testing", and "invariant suite".
asc-shots-pipeline
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…
terraform-skill
Terraform infrastructure as code best practices.
endpoint-validator
Deterministic API endpoint validation with pass/fail reporting.
qa-manual-istqb
Create QA artifacts from requirements: test plans, test conditions/cases, bug reports, regression suites, traceability, and exploratory charters. Use for test planning, test design, defects, coverage, or QA deliverables. Applies ISTQB risk-based techniques and loads templates only when needed. Keywords: test plan…
webapp-selenium-testing
Author and maintain versioned Selenium WebDriver tests with Java and JUnit 5. Use for creating, debugging, or running Selenium specs, implementing Page Objects, handling explicit waits, capturing screenshots, or setting up Maven test projects. Supports Chrome, Firefox, and Edge. Keywords: Selenium WebDriver, Java…