Перейти к содержимому
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/offensive-orchestrationРазведка и OSINT

offensive-orchestration

⁨Coordinate agents across security investigations, assessments, and labs: divide attack-path work, manage shared target sessions, and reconcile evidence across assets, identities, and attempts.⁩

v2026.11.13-21cd5683 установки+3 за 7 дней39 ЗвездыMITсинхронизировано 10 часов назад

Установка

Ещё нет NotHoly CLI? Сначала установите её.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/offensive-orchestration

Пишет в ⁦~/.notholy/skills⁩ после проверки подписи и SHA-256.

ПодписьПодписано, ed25519
kYk0QNGZ6k…fMoAzbDA==CLI проверяет SHA-256 и подпись, прежде чем записать хоть один файл.
Пакет98b636b8…e5332ee2
98b636b8bac6…8bdbe5332ee21 файл · ⁦2.8 KB⁩
ПроверкаНизкийзамечаний нет
Проверка не нашла в этой версии ничего подозрительного.Вся проверка
Источникgithub.com/AeonDave/malskill/tree/main/knowledge-offensive/offensive-orchestration@21cd568

Эта запись еще не переведена на русский, поэтому показан текст на другом языке: English.

Coordinate the security task through its next verified outcome. Load orchestration for delegation, model/effort selection, scheduling, job lifecycle, and integration; apply the additions below to security state and evidence. Use existing task constraints without inventing new approval stops.

Split investigations around independent state

  • Delegate by asset, trust boundary, artifact, or falsifiable hypothesis with a distinct proof requirement. Parallel static analysis of separate samples or patch pairs often fits; interacting operations on the same process, account, service, or debugger need a single owner or explicit serialization.
  • Launch follow-up work when its prerequisite is established: an artifact exists, a build matches, an identity is confirmed, or a session is usable. A scanner label, worker claim, or suggested attack path is a lead, not that prerequisite.
  • Match the worker to the uncertain part: bounded artifact extraction can use an efficient model; unfamiliar internals, cryptography, exploitability, or ambiguous runtime behavior may need stronger reasoning and domain tools. Agent count does not substitute for expertise.

Route by the question

Give each worker a concrete question, the necessary context, and the relevant skills. Combine skills when a question crosses boundaries; hand work to another worker only when separate context, ownership, or expertise helps.

Question Starting skill
Map assets or investigate public sources recon-technique or osint-technique
Investigate a vulnerability or advisory, or validate supported web impact vuln-research or web-exploit-technique
Assess cloud access, a host session, or an AD path cloud-security-technique, post-exploit-technique, or active-directory-technique
Analyze a mobile app, physical device, binary, or forensic artifact mobile-technique, hardware-technique, reversing-technique, or forensic-technique
Build a CVE inventory or review a public test artifact cve-search or poc-weaponization

Add security context to the job contract

Include only what changes execution or interpretation:

  • Stable asset/sample identity, build or hash, relevant configuration, and observation time. An address, filename, or function offset alone may identify different objects after a change.
  • Network position, identity and privilege, session state, required access, and references to credentials through the approved access mechanism. Keep raw secrets out of broad prompts, logs, and shared notes.
  • The hypothesis, decisive observation and controls, existing evidence, known failed attempts with their conditions, and expected artifacts. Carry the relevant original request/output, trace, sample, or reproduction locator rather than a bare verdict.
  • Mutable resources owned, expected state changes, interference risks, and who verifies restoration or cleanup when required by the task.

Protect attribution and shared state

Assign one owner to a shared debugger, authenticated session, mutable account, or state-changing target operation. Read-only operations can still interfere through load, rate limits, caches, or observation windows; coordinate when that affects validity. Separate worktrees do not separate those resources.

Tag evidence with the job/attempt and relevant target state. Separate competing experiments by timing, input markers, or isolated fixtures so one worker's effect is not credited to another. Preserve raw evidence and append corrections; do not overwrite a finding with a newer unexplained verdict. Revalidate dependent conclusions after a reset, patch, privilege change, or different build.

Reconcile timeout and cancellation against target state before retrying an action that may already have succeeded. Do not reuse a late result until its attempt and environment match the current question. Record failed collection and untested paths as coverage gaps.

Integrate evidence, not verdict counts

Compare conflicting results by identity, build, prerequisites, input, timing, and method. Seek the smallest discriminating check; agreement among workers using the same advisory or scanner is one source. Preserve unresolved alternatives when evidence cannot decide.

Load evidence-before-claims when promoting a lead into a finding or reconciling claims for an engagement report. Separate observed behavior, inferred cause, reachable impact, and untested extensions. Report the achieved objective, evidence, coverage gaps, remaining sessions/jobs, and next useful action.

For investigations spanning many artifacts or sessions, load the operational brain and link job results, consequential routing decisions, and failures into the existing task record. Use handoff for an explicit transfer.

When configuring the agent infrastructure

Enforce tool, credential, filesystem, and network access in the execution layer. Model instructions do not provide isolation; containers alone do not establish the required boundary. Keep privileged control sockets and writable host configuration out of worker environments unless the task requires them.

Review MCP/tool definitions and detect changes. Verify local artifacts where supported; authenticate and govern remote endpoints rather than treating a local checksum as a pin on remote behavior. Load untrusted-input-hygiene when ingesting target output, tool descriptions, shared messages, or worker files; validate their provenance and destination format before use.

Файлы этой версии

Права

ПравоЗаявленоНайдено проверкой
Читает файлыНетНет
Пишет файлыНетНет
Выполняет команды shellНетНет
Ходит в сетьНетНет
Использует коннекторыНетНет
Управляет браузеромНетНет

Замечания проверки

Проверено 13 нояб. 2026 г.

Проверка не нашла в этой версии ничего подозрительного.

Чистая проверка снижает риск, но не доказывает, что пакет безопасен. Читайте то, что ставите.

ВерсияОпубликованаКоммитSHA-256ПодписьИзменение прав
v2026.11.13-21cd56813 нояб. 2026 г.21cd56898b636b8Подписана–

Спрашивайте обо всём, что позволяет ваш скоуп.

Создайте аккаунт, пополните баланс и задайте первый вопрос в чате или в терминале.

  1. 1/3

    Создайте аккаунт

    Личный или для компании. Позже можно перейти на аккаунт компании без потери баланса и ключей.

    ЛичныйКомпания
  2. 2/3

    Пополните баланс

    Картой. Оплата за токены, без подписки.

    $5.00минимальное пополнение
  3. 3/3

    Спрашивайте

    В чате, или установите CLI и выполните notholy login в терминале.

    $ notholy login