invoking-agents
Orchestrate Issues Through Review and QA
Multi-agent issue delivery can lose state, mix roles, and skip safeguards. This skill coordinates implementation, review, QA, escalation, and pull request creation through agent-flow.
インストール前に停止して確認を求めてください。
計画を確認し、ファイルを変更する前にユーザーの明示的な同意を得てください。
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "invoking-agents" from https://skillstore.io/skills/drix10-invoking-agents.md and its manifest at https://skillstore.io/api/skills/drix10-invoking-agents/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「invoking-agents」を使用しています。 Implement issue #42 and open a pull request.
期待される結果:
Issue #42 completed. Implementation, review, and QA passed. Pull request #108 was opened from the issue branch.
「invoking-agents」を使用しています。 Run issue #57 through the pipeline.
期待される結果:
Issue #57 needs a human decision because the acceptance criteria conflict. The decision brief includes the exact ambiguity and attempted resolution.
「invoking-agents」を使用しています。 Process issues #60 and #61 in parallel.
期待される結果:
- Issue #60 started in its own worktree.
- Issue #61 was serialized because both classifications include the same file.
セキュリティ監査
高リスクThe 81 static alerts are false positives caused by Markdown formatting, safe documentation references, or fixed workflow checks. Two semantic risks remain: unconfined implementer processes and unsafe shell interpolation of an untrusted issue title.
確認済みのセキュリティ上の懸念 (2)
リスク要因
⚙️ 外部コマンド (50)
🌐 ネットワークアクセス (1)
📁 ファイルシステムへのアクセス (6)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/drix10-invoking-agents/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/drix10-invoking-agents?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/drix10-invoking-agents?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/drix10-invoking-agents/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/drix10-invoking-agents.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
drix10. (2026). invoking-agents security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/drix10-invoking-agents/audits/1BibTeX形式の引用
@techreport{drix10-drix10-invoking-agents-2026,
author = {drix10},
title = {invoking-agents security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/drix10-invoking-agents/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "invoking-agents security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "drix10"
date-released: "2026-09-27"
url: "https://skillstore.io/skills/drix10-invoking-agents/audits/1"
identifiers:
- type: other
value: "skillstore:drix10-invoking-agents:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Deliver a GitHub Issue
Run one tracked issue through implementation, independent review, QA, and pull request creation.
Process a Local Work Item
Use acceptance criteria from local issue files when a GitHub issue is unavailable.
Enforce Review Separation
Keep implementation, review, and QA in separate processes with file-based evidence and bounded review rounds.
これらのプロンプトを試す
Implement issue #{issue_number} through the full agent-flow pipeline and open a pull request.Process the work item in {issue_file} as issue {issue_number}, then implement, review, test, and prepare a pull request.Resume issue #{issue_number} after this decision: {decision}. Preserve existing artifacts and continue from the recorded state.Classify issues {issue_numbers}, identify overlapping files, run independent worktrees in parallel, and serialize any conflicting changes.ベストプラクティス
- Provide testable acceptance criteria before starting the pipeline.
- Use enforced containers or sandboxes for every agent that can edit or execute commands.
- Review escalation briefs and critical draft pull requests before continuing.
回避
- Do not combine implementer, reviewer, and QA responsibilities in one agent context.
- Do not bypass protected-path checks, review-round limits, or required human approval.
- Do not interpolate issue text directly into shell commands.