Skip to content
Back to search

beril

SkillWorks with Claude CodeGitHub

Build and refresh a cybersecurity intelligence base with Camoufox. Harvests anti-bot forums, disclosed reports, researcher blogs and GitHub tool shelves; profiles experts; extracts their methods; writes an evidence-linked dossier; and runs a read-only scan of an app you own. Use for bug bounty recon, pentest planning, threat research, expert tracking, tool selection, application security checks, or when a security site blocks ordinary scraping. Turkish triggers: siber güvenlik araştırması, forum toplama, uzman profili, tool kataloğu, metod çıkarma, bug bounty keşif, uygulama taraması.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sheduxdev--beril/badge.svg)](/listings/sheduxdev--beril)

HTML

<a href="/listings/sheduxdev--beril"><img src="/api/listings/sheduxdev--beril/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

git clone https://github.com/sheduxdev/beril.git
cd beril

python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
camoufox fetch

python scripts/validate.py
python scripts/build_dossier.py --data data --out examples/dossier.md

Then refresh one layer:

python scripts/harvest.py forums --sources 0x00sec,htb,reddit,hackerone --limit 20
python scripts/harvest.py experts --sources curated,hackerone,portswigger --limit 40
python scripts/harvest.py tools --sources canonical --limit 60
python scripts/harvest.py methods --limit 20

Or use the short targets:

make validate
make dossier
make forums

Read `SKILL.md` for the full loop and the quality gates.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 303 lines
  1. ---
  2. name: beril
  3. description: Build and refresh a cybersecurity intelligence base with Camoufox. Harvests anti-bot forums, disclosed reports, researcher blogs and GitHub tool shelves; profiles experts; extracts their methods; writes an evidence-linked dossier; and runs a read-only scan of an app you own. Use for bug bounty recon, pentest planning, threat research, expert tracking, tool selection, application security checks, or when a security site blocks ordinary scraping. Turkish triggers: siber güvenlik araştırması, forum toplama, uzman profili, tool kataloğu, metod çıkarma, bug bounty keşif, uygulama taraması.
  4. ---
  5. # Beril
  6. Beril is a research loop for offensive security intelligence. It uses Camoufox, a patched Firefox with Playwright, to read sites that block plain HTTP clients. It stores what it finds as four linked catalogs: forums and threads, experts, tools, and methods. The output is a dossier you can defend line by line because every entry has a public URL.
  7. Use it when you need current field knowledge rather than a static list. Examples: choosing recon tools for a target, learning how top hunters approach a vulnerability class, tracking a researcher's recent work, or building a reading queue before an engagement.
  8. ## When to use
  9. - A bounty program starts and you want the current tools and methods for its stack.
  10. - A security site returns 403, a Cloudflare challenge, or an empty JavaScript shell to curl.
  11. - You need to turn scattered forum posts and disclosures into a ranked reading list.
  12. - You want to compare experts by what they publish, not by follower count.
  13. - You are preparing a pentest and need a phase-by-phase tool chain with install commands.
  14. - A previous dossier is older than 30 days and the stars, reports, or threads have moved.
  15. Skip Beril when a single page answers the question. Open the page, read it, and leave the catalog alone.
  16. ## Install
  17. ```bash
  18. python -m venv .venv
  19. source .venv/bin/activate
  20. pip install -U "camoufox[geoip]" beautifulsoup4 lxml
  21. camoufox fetch
  22. ```
  23. `camoufox fetch` downloads the browser and GeoIP database. It needs about 300 MB. On a headless Linux box, install `xvfb` if you want the headful fallback for challenge pages.
  24. Run everything from the skill directory:
  25. ```bash
  26. cd skills/beril
  27. python scripts/validate.py
  28. ```
  29. ## One-click scan
  30. For a first pass on an application or artifact you own:
  31. ```bash
  32. ./install.sh
  33. ./beril scan --target https://your-app.example
  34. ./beril scan --target ./build/app.apk
  35. ./beril scan --target ./source --tools
  36. ./beril scan --target ./release/app.exe
  37. ```
  38. The scanner is read-only and static for local files. Web scans report headers, TLS, cookies, exposed paths and fingerprints. Artifact scans read manifests, hardening flags, secrets, dangerous sinks, and archive paths. Add nuclei for a known-CVE pass on a running app. Walkthroughs are in `docs/one-click.md` and `docs/scan-artifacts.md`.
  39. ## Ten-minute run
  40. ```bash
  41. # 1. Pull the current public surface
  42. python scripts/harvest.py forums --sources 0x00sec,htb,reddit,hackerone --limit 25
  43. python scripts/harvest.py experts --sources curated,hackerone,portswigger --limit 40
  44. python scripts/harvest.py tools --sources canonical --limit 60
  45. python scripts/harvest.py methods --limit 20
  46. # 2. Turn the best URLs into notes with headings and code density
  47. python scripts/extract.py --input data/threads.jsonl --out data/thread_details.jsonl --limit 25
  48. # 3. Build the reading dossier
  49. python scripts/build_dossier.py --data data --out examples/dossier.md
  50. # 4. Check schema and prose
  51. python scripts/validate.py
  52. ```
  53. All commands accept `--headful`, `--delay`, `--cache`, and `--fresh`. The cache is keyed by URL hash and lives in `raw/`.
  54. ## The loop
  55. ### 1. Scope the question
  56. Write one sentence before touching a browser: "I need the current external recon method for GraphQL APIs on bug bounty programs." A vague goal produces a 400-row dump nobody reads.
  57. Then pick the layers that can answer it:
  58. | Question | Layers | First sources |
  59. |---|---|---|
  60. | What is being found now? | Threads, reports | HackerOne Hacktivity, r/bugbounty, 0x00sec |
  61. | Who knows this best? | Experts | PortSwigger authors, Intigriti spotlights, report authors |
  62. | What should I run? | Tools | ProjectDiscovery, GitHub topics, canonical shelf |
  63. | How do they do it? | Methods | Researcher blogs, conference talks, docs |
  64. Two layers are enough for a focused brief. Use all four for a new target or a quarterly refresh.
  65. ### 2. Collect with Camoufox
  66. Use the harvesters first. They know the site quirks: Discourse JSON, Ghost RSS, Reddit shadow DOM, HackerOne's disclosure grid.
  67. ```bash
  68. python scripts/harvest.py forums --sources hackerone --limit 50
  69. python scripts/harvest.py experts --sources hackerone --limit 60
  70. ```
  71. The browser is shared across a run. Keep concurrency low. One request every 1 to 2 seconds per host is polite and usually enough to avoid a challenge.
  72. ### 3. Extract, do not summarize yet
  73. `extract.py` records structure: title, headings, intro, code block count, table count. Structure tells you whether a page contains a reproducible method or only commentary. A page with 12 headings and 40 code blocks is worth reading. A page with one heading and no code is a news item.
  74. ```bash
  75. python scripts/extract.py --input data/methods.jsonl --out data/method_details.jsonl --limit 30
  76. ```
  77. Read the top 10 notes yourself. Beril cannot tell whether a technique is correct; it can only show you where the evidence is.
  78. ### 4. Verify the claim
  79. For every method you keep, answer four questions in the note:
  80. 1. What is the precondition? Version, configuration, role, feature flag.
  81. 2. What is the smallest request or command that shows the behavior?
  82. 3. What is the observable proof? Response diff, callback, log line, screenshot.
  83. 4. What makes it fail? WAF, parser choice, cache, patched version.
  84. If the source does not answer them, mark the gap. Do not fill it with plausible detail.
  85. ### 5. Write the dossier
  86. `build_dossier.py` gives you coverage counts, ranked threads, expert reading, a tool shelf, and a method index. Add a short "what changed" section by hand. State the date, the sources you actually reached, and what you could not reach.
  87. ### 6. Refresh
  88. Monthly is enough for tools and experts. Weekly is better for disclosed reports and forum threads. Store each snapshot with its date. When a star count or report page changes, the old dossier still records what you saw.
  89. ## Source board
  90. | Source | Access | Take | Watch out |
  91. |---|---|---|---|
  92. | 0x00sec | Ghost RSS and tag pages | Low-level exploitation, reverse engineering, red team | Editorial account posts most items; read the byline in the body |
  93. | Hack The Box Forum | Discourse JSON | Lab questions, certification talk, beginner paths | Many threads are single-question homework |
  94. | Reddit r/netsec, r/bugbounty | `sh.reddit.com`, shadow DOM | Field reports, disclosure drama, methodology threads | Comment text bleeds into post text; trim before quoting |
  95. | HackerOne Hacktivity | Public disclosure grid | Real report titles, weakness, severity, bounty, author | Report bodies often need login; the grid metadata is public |
  96. | Intigriti researchers blog | Public listing and RSS | Writeups, hacker interviews, tool reviews | Category pages mix news with technique |
  97. | PortSwigger Research | Author pages and RSS | Web exploitation primitives, desync, XSS, cache | Listing includes topic hubs; filter to article URLs |
  98. | ProjectDiscovery blog | Public listing | Recon tooling, nuclei templates, AI pentest benchmarks | Product posts outnumber method posts |
  99. | YesWeHack blog | Public categories | Bug bounty lessons, Dojo challenges | Some articles are program news |
  100. | Bugcrowd VRT | Public taxonomy | Severity language and report classification | Not a forum |
  101. | DEF CON media | Public directory index | Talks and slides by year | Large files; index only unless you need the talk |
  102. | GitHub topics | Public HTML | Tool discovery and rough popularity | Topic tags are noisy; verify the repo does security work |
  103. | Hacker News, Lobsters | Public | Practitioner discussion, postmortems | Signal is uneven; use as a lead generator |
  104. More detail, including endpoints and query strings, is in `references/forums.md`.
  105. ## Entity rules
  106. Keep the same shape across runs. The scripts already write these fields.
  107. ### Thread or report
  108. ```json
  109. {"type":"thread","source":"HackerOne Hacktivity","url":"https://hackerone.com/reports/...",
  110. "title":"...","author":"handle","date":"","tags":["disclosed"],
  111. "summary":"...","metrics":{"program":"...","weakness":"...","severity":"High","bounty":"$2,000"},
  112. "collected_at":"2026-11-22T00:00:00+00:00"}
  113. ```
  114. A thread is any public discussion unit: forum post, disclosed report, blog article with comments. Do not store comment trees unless the comment adds a reproduction detail.
  115. ### Expert
  116. ```json
  117. {"type":"expert","source":"PortSwigger Research","name":"James Kettle",
  118. "handle":"albinowax","profile":"https://portswigger.net/research/james-kettle",
  119. "focus":"request smuggling, cache poisoning, desync",
  120. "works":[{"title":"HTTP/2: The Sequel is Always Worse","url":"..."}],
  121. "collected_at":"..."}
  122. ```
  123. `focus` describes what the person publishes. Do not invent a biography, employer, or country. If the only evidence is a report handle, write that.
  124. ### Tool
  125. ```json
  126. {"type":"tool","source":"canonical","category":"recon","repo":"https://github.com/projectdiscovery/subfinder",
  127. "name":"projectdiscovery/subfinder","description":"Fast passive subdomain enumeration tool.",
  128. "stars":"14845","language":"Go","install":["go install ..."],"flags":[],"collected_at":"..."}
  129. ```
  130. Star counts are a snapshot. Label them with the collection date in any prose. A repo with no README or a last release from years ago is still useful, but say so.
  131. ### Method
  132. ```json
  133. {"type":"method","source":"PortSwigger Research","url":"...","title":"...",
  134. "headings":["..."],"intro":"...","code_blocks":42,"tables":3,"collected_at":"..."}
  135. ```
  136. A method note is not a summary of the article. It is the transferable procedure plus the evidence that it worked.
  137. ## Camoufox rules
  138. The full playbook is in `references/camoufox-playbook.md`. The short version:
  139. - Keep the fingerprint consistent. One locale, one timezone, one OS, one browser version per session.
  140. - Start headless with `humanize=True`. Move to headful only when a challenge persists.
  141. - Warm the origin before fetching an RSS or JSON endpoint from page context.
  142. - Prefer the site's JSON or RSS endpoint over the rendered page.
  143. - Wait for a selector, not for `networkidle`. Security sites keep analytics and websockets open.
  144. - Cache every response. Re-parsing should not require a second request.
  145. - Back off on 403, 429, and 503. Three attempts with growing delays is enough.
  146. - Do not solve CAPTCHAs with paid services unless the engagement allows it.
  147. - One identity per session. Rotating proxies and user agents inside one run creates more suspicion than it removes.
  148. For shadow DOM sites such as Reddit, read the host element with `inner_text`. BeautifulSoup sees the light DOM only.
  149. ## Writing rules
  150. The dossier is read by a human under time pressure. Apply the humanizer rules while writing:
  151. - State the fact. Cut filler such as "it is important to note".
  152. - No em dashes or en dashes. Use a period, comma, colon, or parentheses.
  153. - Avoid the "X, but Y" contrast unless the negative half corrects a real belief.
  154. - No triad for rhythm. Two items or four are fine.
  155. - Sentence case headings. No decorative emoji.
  156. - Straight quotes. No curly quotes.
  157. - Every technique claim links to the source that showed it.
  158. - Separate observation from inference: "The report shows X. This suggests Y, which I did not test."
  159. - Short paragraphs. A 40-word paragraph beats a 120-word wall when the reader is scanning for a command.
  160. Run the humanizer skill on long narrative sections when it is available. Tables and command blocks do not need a style pass.
  161. ## Quality gates
  162. Do not publish a dossier until all of these pass.
  163. | Gate | Test |
  164. |---|---|
  165. | Traceability | Every row has a public URL and a collection timestamp |
  166. | Coverage | At least three source types across the four layers |
  167. | Duplicates | Under 10 percent duplicate URLs after the merge |
  168. | Freshness | Reports and threads from the last 12 months dominate |
  169. | Evidence | Every method card names a precondition and a proof |
  170. | Safety | No credentials, tokens, private reports, or personal data |
  171. | Reproducibility | Every command in the dossier was run in this environment |
  172. | Prose | `validate.py` reports zero em dashes and no schema errors |
  173. Use `python scripts/validate.py --links --max-links 40` before publishing. A dead link is acceptable if you note it. A dead link presented as live is not.
  174. ## Outputs
  175. - `examples/dossier.md` is the human brief.
  176. - `data/*.jsonl` is the machine catalog.
  177. - `raw/` is the response cache and the audit trail.
  178. - `evidence/` holds screenshots and DOM snapshots for claims that may change.
  179. Keep the dossier and the JSONL in sync. If you edit a fact by hand, edit the row that produced it or add a note explaining the override.
  180. ## Commands
  181. ```bash
  182. # Harvest one layer
  183. python scripts/harvest.py forums --sources 0x00sec,htb,reddit,hackerone,intigriti
  184. python scripts/harvest.py experts --sources curated,hackerone,portswigger,intigriti
  185. python scripts/harvest.py tools --sources canonical,topics --limit 80
  186. python scripts/harvest.py methods --limit 25
  187. # Harvest everything into data/
  188. python scripts/harvest.py all --out-dir data --limit 30
  189. # Deep-read the best URLs
  190. python scripts/extract.py --input data/methods.jsonl --out data/method_details.jsonl --limit 30
  191. python scripts/extract.py --url https://0x00sec.org/some-post/ --out /tmp/note.json
  192. # Assemble and check
  193. python scripts/build_dossier.py --data data --out examples/dossier.md
  194. python scripts/validate.py
  195. # Read-only application and artifact scan
  196. ./beril scan --target https://your-app.example --out scans/myapp
  197. ./beril scan --target ./build/app.apk --out scans/app
  198. ./beril scan --target ./source --tools --out scans/source
  199. ./beril scan --target ./bin/service --out scans/service
  200. ```
  201. ## Reference map
  202. | File | Use |
  203. |---|---|
  204. | `references/camoufox-playbook.md` | Browser settings, challenge ladder, site recipes, failure modes |
  205. | `references/forums.md` | Community catalog, endpoints, what to mine, etiquette |
  206. | `references/experts.md` | Researcher profiles and signature methods |
  207. | `references/tooling.md` | Phase map, install commands, tool chains |
  208. | `references/techniques.md` | Method cards for web, API, cloud, AD, mobile, binary, AI |
  209. | `references/source-catalog.md` | Every feed, API, archive and upstream skill repo |
  210. | `references/dossier-template.md` | Output structure and section prompts |
  211. | `references/scoring.md` | Ranking and keep/drop rules |
  212. | `docs/one-click.md` | Install, scan and troubleshoot without the terminal |
  213. | `docs/scan-artifacts.md` | APK, IPA, PE, ELF, archive and source review |
  214. | `agents/` | Prompts for parallel forum, expert, tool and method research |
  215. ## Legal and ethical bounds
  216. Collect only public pages. Respect robots.txt, terms of service, and rate limits. Do not bypass a login to reach a report, and do not scrape private program data. Quote short excerpts with a link; do not republish whole articles. Keep personal data out of the catalog unless the person published it for professional use. When in doubt, link and paraphrase.
  217. Testing techniques from the catalog against a target still requires authorization. A method card is not a license.
README.md · README · 204 lines
  1. # Beril
  2. ![Beril, green eyes and pistachio](assets/beril.webp)
  3. A cybersecurity intelligence skill that reads the web with Camoufox, keeps what it finds as evidence-linked catalogs, and turns the result into a dossier a human can act on. The palette is pistachio green and the eyes are green, because the project is named after someone who likes both.
  4. Beril was built from 43 public security skill repositories and a live collection pass over forums, disclosed reports, researcher blogs, and GitHub tool shelves.
  5. ## Why it exists
  6. Two problems get in the way. Security sites block plain HTTP clients, and the reading lists people keep are stale or unsourced. Beril uses Camoufox for the first, stores every item with a date and URL for the second, and turns the result into a short dossier with a reading queue, a tool shelf, and method cards that name a precondition and a proof.
  7. ## What's inside
  8. ```text
  9. beril/
  10. ├── SKILL.md # the agent-facing skill
  11. ├── scripts/
  12. │ ├── camo.py # Camoufox session, cache, parsing helpers
  13. │ ├── harvest.py # forums, experts, tools, methods
  14. │ ├── extract.py # headings, intros, code density
  15. │ ├── scan.py # URL or artifact router
  16. │ ├── scan_app.py # read-only web scan
  17. │ ├── scan_artifact.py # APK, IPA, PE, ELF, archive, source scan
  18. │ ├── build_dossier.py # JSONL -> Markdown brief
  19. │ └── validate.py # schema, links, prose checks
  20. ├── install.sh # one-click setup
  21. ├── beril # command wrapper
  22. ├── docs/one-click.md # install and scan without the terminal
  23. ├── docs/scan-artifacts.md # APK, binary and source review
  24. ├── references/
  25. │ ├── camoufox-playbook.md # challenge ladder and site recipes
  26. │ ├── forums.md # community catalog
  27. │ ├── experts.md # researcher profiles and methods
  28. │ ├── tooling.md # phase map and commands
  29. │ ├── techniques.md # 25 method cards
  30. │ ├── source-catalog.md # provenance and upstream repos
  31. │ ├── dossier-template.md # output structure
  32. │ └── scoring.md # ranking rules
  33. ├── agents/ # parallel research prompts
  34. ├── assets/ # banner and social preview
  35. ├── data/ # snapshot catalogs
  36. ├── examples/dossier.md # generated sample brief
  37. ├── examples/scan-example.md # sample web scan
  38. ├── examples/scan-artifact-example.md # sample source scan
  39. └── requirements.txt
  40. ```
  41. ## One-click scan
  42. ```bash
  43. git clone https://github.com/sheduxdev/beril.git
  44. cd beril
  45. ./install.sh
  46. ./beril scan --target https://your-app.example
  47. ```
  48. The scan is read-only and works on a URL, APK, IPA, PE/EXE/DLL, ELF binary, archive, or source tree. For web targets it checks headers, TLS, cookies, a short list of exposed paths, and fingerprints. For artifacts it reads the manifest or binary, finds secrets and dangerous sinks, and checks hardening flags. Open the Markdown report in `scans/`. See `docs/one-click.md` and `docs/scan-artifacts.md` for the walkthrough and the limits.
  49. ```bash
  50. ./beril scan --target ./build/app.apk
  51. ./beril scan --target ./source --tools
  52. ./beril scan --target ./release/app.exe
  53. ```
  54. Optional known-CVE pass, if nuclei is installed:
  55. ```bash
  56. nuclei -u https://your-app.example -severity medium,high,critical \
  57. -tags cve,exposure,misconfig -o scans/nuclei.txt
  58. ```
  59. ## Manual quick start
  60. ```bash
  61. git clone https://github.com/sheduxdev/beril.git
  62. cd beril
  63. python -m venv .venv
  64. source .venv/bin/activate
  65. pip install -r requirements.txt
  66. camoufox fetch
  67. python scripts/validate.py
  68. python scripts/build_dossier.py --data data --out examples/dossier.md
  69. ```
  70. Then refresh one layer:
  71. ```bash
  72. python scripts/harvest.py forums --sources 0x00sec,htb,reddit,hackerone --limit 20
  73. python scripts/harvest.py experts --sources curated,hackerone,portswigger --limit 40
  74. python scripts/harvest.py tools --sources canonical --limit 60
  75. python scripts/harvest.py methods --limit 20
  76. ```
  77. Or use the short targets:
  78. ```bash
  79. make validate
  80. make dossier
  81. make forums
  82. ```
  83. Read `SKILL.md` for the full loop and the quality gates.
  84. ## Research loop
  85. 1. **Scope.** One sentence, one target class, one time window.
  86. 2. **Collect.** Camoufox reads RSS, JSON, shadow DOM, and challenge pages. Every response is cached by URL hash.
  87. 3. **Extract.** Headings, intro, code block count, and table count separate a method from a news item.
  88. 4. **Verify.** A method card needs a precondition, a minimal request, an observable proof, and a failure mode.
  89. 5. **Write.** The dossier links every claim. Observations and inferences sit in separate sentences.
  90. 6. **Refresh.** Weekly for reports and threads, monthly for tools, quarterly for standards.
  91. ## The four catalogs
  92. | Layer | Snapshot | What it answers |
  93. |---|---:|---|
  94. | Threads and reports | 311 | What is being found now? |
  95. | Experts | 94 | Who knows this best? |
  96. | Tools | 87 | What should I run? |
  97. | Methods | 85 | How do they do it? |
  98. The snapshot is a sample, not a census. See `references/source-catalog.md` for endpoints, dates, and gaps.
  99. ## Camoufox
  100. Beril uses Camoufox because ordinary HTTP clients fail on the sources that matter. The playbook covers:
  101. - fingerprint consistency across locale, timezone, OS, and proxy;
  102. - headless to headful escalation under Xvfb;
  103. - persistent profiles for challenge clearance;
  104. - Discourse JSON, Ghost RSS, Reddit shadow DOM, HackerOne's disclosure grid, GitHub stars and READMEs;
  105. - caching, evidence snapshots, rate limits, and the failure modes that look like empty pages.
  106. Start with `references/camoufox-playbook.md`.
  107. ## Research base
  108. The build downloaded 43 public repositories and found 22,976 `SKILL.md` files across 21 of them. The upstream corpus includes:
  109. - broad libraries: `mukul975/anthropic-cybersecurity-skills`, `ComeOnOliver/skillshub`;
  110. - focused packs: `uphiago/recon-skills`, `Security-Talent/bugskill-ai`, `penligent/AIPentest_Skills`;
  111. - agent systems: `KeygraphHQ/shannon`, `usestrix/strix`, `vxcontrol/pentagi`, `xalgorix/xalgorix`;
  112. - reference data: `swisskyrepo/PayloadsAllTheThings`, `danielmiessler/SecLists`, `arkadiyt/bounty-targets-data`.
  113. The full list, counts, and roles are in `references/source-catalog.md`.
  114. ## Evidence rules
  115. - Every row has a public URL and a collection timestamp.
  116. - A technique claim needs one grade A source or two independent grade B sources.
  117. - Star counts and report totals are snapshots. The date travels with the number.
  118. - No private reports, credentials, tokens, or personal data.
  119. - A dead link is noted, not hidden.
  120. - Prose follows the humanizer rules: no em dashes, no forced triads, no inflated significance.
  121. ## Example output
  122. `examples/dossier.md` is generated from the snapshot. It shows coverage, high-signal threads, expert reading, a tool shelf, a method index, and the gaps left for the next pass.
  123. ## Requirements
  124. - Python 3.10 or newer
  125. - `camoufox[geoip]`, `beautifulsoup4`, `lxml`
  126. - About 300 MB for the Camoufox browser
  127. - `xvfb` for the headful fallback on Linux
  128. ## The name
  129. Beril is a person, not an acronym. She has green eyes and likes pistachios, so the banner does too. The rest of the repository is evidence.
  130. The banner is in `assets/beril.webp` (PNG fallback in `assets/beril.png`). The GitHub social preview is `assets/social-preview.jpg`.
  131. ## License
  132. MIT for the code and original prose. The linked sources and cloned repositories keep their own licenses. See `LICENSE`.
  133. ## Contributing
  134. Useful contributions:
  135. - a new source with a tested endpoint and a note on its access limits;
  136. - a correction to a method card with a primary link;
  137. - a tool entry with a verified install command;
  138. - a failure mode that the playbook does not cover.
  139. Please keep the schema, date your snapshot, and run `python scripts/validate.py` before opening a pull request.
  140. ## Türkçe
  141. Beril, Camoufox ile siber güvenlik forumlarını, açıklanmış raporları, araştırmacıları ve araçları toplayan bir araştırma becerisidir. Bulduğunu kaynak bağlantısı ve tarihle saklar, sonunda okunabilir bir dosya üretir.
  142. Kurulum:
  143. ```bash
  144. python -m venv .venv
  145. source .venv/bin/activate
  146. pip install -r requirements.txt
  147. camoufox fetch
  148. ```
  149. Kullanım için `SKILL.md` dosyasına, kaynak listesi için `references/forums.md` dosyasına bak. Metot kartları `references/techniques.md` içinde. Veri anlık görüntüsü `data/` altında.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.