233 件（tonydzi のリポジトリ） ・ 人気順
概要と使いどころ
- Find leaked or mentioned selectors circulating in pastes, leak forums, Telegram channels and dump markets, and judge whether a claimed leak is genuine or a recycled combolist. Use when checking whether a name, email, domain or credential is circulating, verifying a breach claim made against your organisation, or setting up ongoing leak monitoring
日本語の概要は準備中です。原文の説明を表示しています。
- Фандрайз по методике Гонки: упаковать НАШ рейз/анонс/заголовок по каталогу приёмов Gonka/Либерманов (журналистское досье, anton голосом 26.08.2026)… Триггеры: “/gonka-fundraise“, “/gonka“, “гонка фандрайз“, “фандрайз по типу гонки“, “упакуй рейз“, “упакуй раунд“, “как подать сумму“, “заголовок про деньги“, “проверь их фандрайз“, “пирамида или продукт“, “package the raise“, “fundraise like gonka“
日本語の概要は準備中です。原文の説明を表示しています。
- Craft advanced search-engine queries and Google dorks to surface hidden files, documents and mentions. Use when building a Google dork, hunting a leaked document, or searching paste sites and document repositories for a name, email or selector
日本語の概要は準備中です。原文の説明を表示しています。
- Enumerate an organisation's subdomains and sibling domains from Certificate Transparency logs and passive DNS, without sending traffic to the target. Use when looking for staging, dev, admin or VPN hosts, mapping the full hostname footprint of a domain, or spotting infrastructure a company forgot it had
日本語の概要は準備中です。原文の説明を表示しています。
- Find internet-exposed hosts, ports, services and devices using third-party internet-scan data instead of touching the target. Use when asked what a company has exposed to the internet, to check open ports on an IP or netblock, or to write a Shodan filter query
日本語の概要は準備中です。原文の説明を表示しています。
Read who commented on recent Facebook posts and publish personalized replies through the real logged-in Chrome tab, draft-first, with a daily cap and a minimum gap between replies. Triggers: "/fb-reply", "reply to my facebook comments".
日本語の概要は準備中です。原文の説明を表示しています。
Investigate the root cause of a recurring or systemic defect across a series of incidents, not a single one. Use on the third recurrence, or when someone asks 'why again?', 'five whys', 'fix the root'. Skip for one or two ordinary cases, an already proven simple cause, or a one-off external outage. Triggers: /five-whys, five whys, fix the root.
日本語の概要は準備中です。原文の説明を表示しています。
Default to Firefox for browser automation and decide when Chrome is truly required. Use before any task that needs a browser: fetching a page, grabbing cookies, headless runs, logging into a site. Includes a matrix of which tasks must stay on Chromium and why. Triggers: /firefox, /ff, via firefox, need a browser, headless browser, which browser to use, browser automation.
日本語の概要は準備中です。原文の説明を表示しています。
Find a person, lead, contact or company by name in any spelling: a deterministic search that catches transliteration across alphabets, wrong-keyboard-layout typing and typos. This is the exact-name lane (zero tokens), complementary to semantic vault search. Triggers: "/find <name>", "show everyone named <X>".
日本語の概要は準備中です。原文の説明を表示しています。
Publish an already-vetted post to a personal Facebook wall through the owner's real logged-in Chrome tab (a low-ban-risk path), rate-limit-guarded and draft-first: paste, verify what is actually in the composer, confirm after reload. Triggers: "/fb-post", "publish to facebook", "post this to my wall".
日本語の概要は準備中です。原文の説明を表示しています。
ОТДЕЛЬНАЯ ДВЕРЬ под GitHub Discussions — Q&A-поверхность, где ответ помечается как «Answer», у автора ответа растёт… Триггеры: “/gh-discussions“, “/ghd“, “/discussions“, “дискуссии на гитхабе“, “ответь в discussions“, “где нас ждут вопросы“, “найди Q&A под наш опыт“, “github discussions“, “answer a discussion“, а также САМ, когда наш артефакт отвечает на чей-то ВОПРОС (а не чинит чей-то баг)
日本語の概要は準備中です。原文の説明を表示しています。
Import a GitBook space (company docs, a whitepaper) into an Obsidian vault as linked atomic notes plus a map-of-content, concept links and a RAG reindex. Idempotent re-import supported. Triggers: "/gitbook-import <url>", "import this gitbook", "gitbook to vault".
日本語の概要は準備中です。原文の説明を表示しています。
КАК МЫ ДВОЕ (Антон + Макс) продвигаемся на GitHub — рабочий манифест лейнов, не теория. Триггеры: /github-growth, /ghg, «как продвигаться на гитхабе», «прокачаем гитхаб», «партизанский гитхаб», «что делаем на гитхабе сегодня», «github strategy», а также САМ перед любой волной GitHub-активности
日本語の概要は準備中です。原文の説明を表示しています。
Check, search or digest Gmail across several mailboxes over the owner's own OAuth connector, with no browser and near-zero tokens for the raw pull. Read-only by default: drafting and sending go through the outbound approval gate. Triggers: "/gmail", "check mail", "any important emails", "find the email about <X>".
日本語の概要は準備中です。原文の説明を表示しています。
LLM-judge stage of an alpha-mining pipeline: take a miner's deterministic candidate list, keep only real signal, drop noise, and propose additions to that miner's curated note. Use after any zero-token detector run. Reads only the candidate digest and the home note, never the corpus. Triggers: "/alpha-judge <miner>", "judge the candidates".
日本語の概要は準備中です。原文の説明を表示しています。
Find and merge duplicate or near-duplicate notes anywhere in a vault (rules, concepts, people, leads) with a deterministic scanner and a supersede-not-delete merge policy. Human review before any merge is written. Triggers: "/dedup", "clean up duplicates", "dedupe <folder>".
日本語の概要は準備中です。原文の説明を表示しています。
Look up the registry of declined and deferred decisions, so the same idea is never re-pitched: what was rejected, why, and under what condition to revisit. Read-only, and can also run the detector for new rejections in recent sessions. Triggers: "/declined", "did we reject this before".
日本語の概要は準備中です。原文の説明を表示しています。
Decide-as-cofounder mode: the owner hands over the decision itself, so the agent does not ask back, does not offer a menu of options and does not wait, but picks, acts and reports the call with its reasoning. Triggers: /decide, /ds, decide yourself, your call, up to you, you know better, do as you see fit.
日本語の概要は準備中です。原文の説明を表示しています。
Repair the Cursor editor when it crashes, fails to launch, or new Agent chats break. Use with a Request ID, fresh logs, CursorRule.parse_error or invalid UTF8 in skill frontmatter, or a better-sqlite3 NODE_MODULE_VERSION mismatch. Finds a reproducible cause, applies a narrow reversible fix and proves it with two new chats. Triggers: /cursor-repair, Cursor won't start, Cursor agent broken.
日本語の概要は準備中です。原文の説明を表示しています。
Creates data visualizations (charts, graphs, tables) optimized for AI engine parsing and citation. Produces inline SVG/HTML with text summaries, data tables, and JSON-LD so AI engines can quote the data.
日本語の概要は準備中です。原文の説明を表示しています。
Verify someone else's code fix against your own live corpora (agent transcripts, sessions, memory files) before trusting or merging it. Use when an external PR or patch touches how transcripts, sessions or agent memory are read. Triggers: /corpus-bench, run it on our corpus, verify the fix on our transcripts, corpus bench.
日本語の概要は準備中です。原文の説明を表示しています。
- СТОРОЖ ВХОДЯЩЕГО ФИДБЭКА: кто из посторонних инженеров пришёл к НАШИМ репозиториям, что написал, сколько часов ждёт… Триггеры: “/contrib-watch“, “/cw“, “кто нам написал“, “проверь входящий фидбэк“, “что там на гитхабе“, “есть ли новые контрибьюторы“, “кто пришёл“, “долги по PR“, “check inbound feedback“, “who contributed“, а также САМ в начале любой сессии, где речь про GitHub, флагман
日本語の概要は準備中です。原文の説明を表示しています。
Drive the current task to a verified result instead of stopping at a plausible report. Use when the user says /continue, keep going, not done yet, push further, or is unhappy with the result. Rebuilds requirements from the conversation, re-checks real state, fixes root causes, verifies from the consumer side, offloads side quests.
日本語の概要は準備中です。原文の説明を表示しています。
After shipping a repo, release or feature, find who on GitHub actually needs it: search issues, discussions and catalogs for the symptom, rank live threads and draft one precise reply per consumer. Use right after any artifact goes public. Triggers: /consumer-hunt, /ch, find consumers, where to submit.
日本語の概要は準備中です。原文の説明を表示しています。