AbuseIPDB API reference. IP reputation and abuse report lookups.
日本語の概要は準備中です。原文の説明を表示しています。
Use when rating a source with the NATO Admiralty Scale, the user asks "is this reliable?" / "rate this source", or the tradecraft pipeline calls for source assessment before publishing. Reliability A-F, credibility 1-6.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Every piece of intelligence entering this platform MUST be assessed using the Admiralty Scale. This is non-negotiable. Tag every item with a two-character code (e.g., B2). Claims from documents are the exception: they carry the evidence grade instead, see below.
The pack uses two instruments. They are not the same and neither is converted into the other.
/quality-of-information-check with the evidence grade. Lookup results and single items are rated here, on the Admiralty scale.This skill is the reference for the Admiralty scale itself: what the letters and digits mean and how to apply them to a single item, such as a lookup result, a feed entry or a tip.
Documents, articles and reports are graded per claim by /quality-of-information-check, using its fixed rubric (references/grading-rubric.md in that skill). That grade is the evidence grade, not an Admiralty rating. It resolves the article to its originating source first, then grades each claim on the chain it arrived through. One report usually contains claims of different standing, so one grade for the whole report is wrong.
The pack does not store reliability opinions about named organisations. Where the guides and examples below name a vendor or agency, they illustrate a kind of access and track record. They are not standing grades for that organisation. In one report the same organisation can publish an observation that /quality-of-information-check grades "direct, firm" and an attribution it grades "direct, tentative".
How trustworthy is the source based on its track record?
| Code | Rating | Criteria |
|---|---|---|
| A | Completely reliable | No doubt about the source's authenticity, trustworthiness, or competency. History of complete reliability. |
| B | Usually reliable | Minor doubt. Source has been reliable in most instances. |
| C | Fairly reliable | Doubt about reliability. Source has provided valid information in the past but not consistently. |
| D | Not usually reliable | Significant doubt. Source has been unreliable in the past. |
| E | Unreliable | Source has a track record of being unreliable, or the information is obtained under duress/deception. |
| F | Reliability cannot be judged | No basis for evaluating the source's reliability. New or unknown source. |
Judge the source on how it knows and how it has performed, not on its name.
How likely is the information itself to be accurate, regardless of source?
| Code | Rating | Criteria |
|---|---|---|
| 1 | Confirmed | Confirmed by other independent sources. Logical, consistent with other information on the subject. |
| 2 | Probably true | Not confirmed, but logical and consistent with other information. |
| 3 | Possibly true | Not confirmed. Reasonably logical but not fully consistent with other information. |
| 4 | Doubtful | Not confirmed. Possible but not logical. No other information on the subject. |
| 5 | Improbable | Not confirmed. Not logical. Contradicted by other information on the subject. |
| 6 | Truth cannot be judged | No basis for evaluating the information's veracity. |
These illustrate the reasoning. They are not standing grades for the organisations named.
| Rating | Example |
|---|---|
| A1 | Microsoft publishes CVE details with MSRC forensic analysis, confirmed by CISA KEV listing |
| B2 | CrowdStrike reports new APT campaign TTPs; consistent with own telemetry but not independently confirmed |
| C3 | Security blogger reports new malware variant with partial technical analysis; plausible but unverified |
| D4 | Anonymous Telegram channel claims zero-day in popular software; no technical details provided |
| F6 | First-time automated feed delivers IOCs with no historical accuracy baseline |
/quality-of-information-check, which grades each claim on the primary's access and wording, plus how faithfully the outlet transmitted it; five outlets covering one report are one source)まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
AbuseIPDB API reference. IP reputation and abuse report lookups.
日本語の概要は準備中です。原文の説明を表示しています。
Analysis of Competing Hypotheses — structured technique for evaluating multiple explanations against evidence. Use when facing ambiguous attribution or multiple plausible scenarios. Prefers graded evidence items from /quality-of-information-check and runs that skill first when handed raw URLs or text. Runs on ungraded evidence when asked, labelled as such, unweighted, and capped at Moderate confidence.
日本語の概要は準備中です。原文の説明を表示しています。
Use when documenting a named campaign across time and victims, the user asks to start or update a campaign record, or another skill identified a multi-incident cluster that warrants formal tracking. Provides the template (timeline, attribution, victimology, attack chain, Diamond Model mapping, IOC clusters) and the lifecycle from active to historical.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks about carding, BIN attacks, payment-card breach markets, fullz/CVV2 trade, autoshops (BidenCash, Brian's Club, Russianmarket, B1ack's Stash), or financial-fraud TTPs. Self-updating knowledge cell.
日本語の概要は準備中です。原文の説明を表示しています。
Censys API v2 reference. Host reconnaissance and certificate data.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks about Chinese state-sponsored cyber operations or specific PRC-aligned actors (APT41, Volt Typhoon, Mustang Panda, APT10, APT31, Salt Typhoon, etc.), MSS/PLA-attributed campaigns, or PRC sector targeting. Self-updating knowledge cell.
日本語の概要は準備中です。原文の説明を表示しています。