Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

ordfsordfs 搜索

Agent Skill

ordfs 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

419

周安装

18

GitHub Stars

2

下载量

147
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ordfs(ordfs 搜索)
来源仓库:https://github.com/b-open-io/bsv-skills
仓库路径:skills/ordfs
安装命令:
npx skills add https://github.com/b-open-io/bsv-skills --skill ordfs
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/b-open-io/bsv-skills --skill ordfs

简介

ordfs 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词或任务场景快速定位候选结果。
  • 通过 npx skills add 命令从指定仓库安装,需结合原始 README 核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • ordfs 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

ORDFS - Ordinals File System

HTTP gateway for accessing on-chain content (inscriptions) from BSV blockchain.

Live Gateway: https://ordfs.network Repository: https://github.com/b-open-io/1sat-stack

Quick Reference

EndpointPurpose
/{txid}_{vout}Direct content access
/content/{pointer}Content with options
/content/{pointer}:{seq}Specific version
/content/{pointer}/{file}File from directory
/preview/{b64Html}Preview HTML code
/v2/metadata/{outpoint}Metadata only

Content Access Patterns

Basic Content URL

https://ordfs.network/{txid}_{vout}

Example:

https://ordfs.network/abc123...def_0

Outpoint Formats

All formats resolve to the same content:

FormatExample
Underscoreabc123..._0
Periodabc123....0
Txid onlyabc123... (defaults to vout 0)

Content Endpoint with Options

/content/{pointer}[:{sequence}][/{filepath}]

Query Parameters:

ParamDefaultDescription
contenttrueInclude content data
mapfalseInclude MAP metadata
outfalseInclude raw output (base64)
parentfalseInclude parent reference
raw-Return directory JSON instead of index.html

Examples:

/content/abc123..._0?map=true          # With MAP metadata
/content/abc123..._0?content=false     # Metadata only
/content/abc123..._0?raw               # Directory listing

Sequence Versioning

Track inscription updates using sequence numbers.

No Sequence (Raw Content)

/content/{pointer}         # Raw content from the outpoint, no origin resolution

Behavior: Returns content directly from the specified outpoint. No crawl is performed.

Sequence Values

SeqBehavior
(none)Raw content from the outpoint, no origin resolution, no crawl
-2Origin only — backward crawl to find origin, returns origin data, no forward crawl
0Resolve at the requested outpoint, also resolves origin to return in metadata
-1Latest state — full forward crawl to current tip
N (positive)Specific sequence in the ordinal's transfer chain
/content/{pointer}:-2      # Origin only
/content/{pointer}:0       # Resolve at outpoint, with origin metadata
/content/{pointer}:-1      # Latest state (full forward crawl)
/content/{pointer}:5       # 5th transfer in chain

Caching

  • Specific sequence (:N where N >= 0): Long TTL (30 days), immutable content
  • Latest (:-1): Short TTL (60s)

Response Headers

HeaderDescription
X-OutpointCurrent outpoint
X-OriginOriginal inscription outpoint
X-Ord-SeqSequence number
X-MapJSON MAP metadata
X-ParentParent inscription outpoint

Directories (ord-fs/json)

Inscriptions with content type ord-fs/json represent directories.

Directory Format

{
  "index.html": "ord://abc123..._0",
  "style.css": "abc123..._1",
  "app.js": "def456..._0"
}

Values can be:

  • ord://txid_vout - Full ordinal reference
  • txid_vout or txid - Direct reference
  • _N - Relative vout reference (resolved to {manifest_txid}_N)

Relative Vout Resolution (_N)

ORDFS natively resolves _N patterns in directory manifests. When an ord-fs/json entry has a value like _1, ORDFS resolves it to {manifest_txid}_1 — the sibling output in the same transaction.

{
  "SKILL.md": "_1",
  "README.md": "_2",
  "lib/utils.ts": "_3"
}

Clients do NOT need to parse the manifest and construct outpoint URLs. Instead, request files by path:

/content/{manifest_outpoint}/SKILL.md      → resolves _1 → {txid}_1
/content/{manifest_outpoint}/lib/utils.ts  → resolves _3 → {txid}_3

Recursive Directory Traversal

ORDFS supports nested directories. If a directory entry points to another ord-fs/json inscription, ORDFS recurses into it automatically:

{
  "SKILL.md": "_1",
  "references": "_2"
}

Where _2 is itself an ord-fs/json manifest:

{
  "api-docs.md": "_1",
  "examples.md": "_2"
}

Accessing /content/{root_manifest}/references/api-docs.md traverses both levels.

Accessing Directory Files

/content/{directory_pointer}/index.html
/content/{directory_pointer}/style.css
/content/{directory_pointer}/app.js

SPA Routing

For SPAs, unknown paths fall back to index.html:

/content/{pointer}/unknown/path  → Returns index.html

Raw Directory JSON

Add ?raw to get the directory listing instead of index.html:

/content/{pointer}?raw

Preview Endpoint

Test HTML inscriptions before broadcasting.

Base64 HTML Preview

/preview/{base64EncodedHtml}

Example:

const html = "<html><body>Hello!</body></html>";
const b64 = btoa(html);
const previewUrl = `https://ordfs.network/preview/${b64}`;

POST Preview

curl -X POST https://ordfs.network/preview \
  -H "Content-Type: text/html" \
  -d "<html><body>Hello!</body></html>"

Recursive Inscriptions

Reference other inscriptions from HTML/JS content.

Pattern

<script src="/content/abc123..._0"></script>
<img src="/def456..._0" />
<link href="/content/style123..._0/main.css" rel="stylesheet">

Base Path Handling

ORDFS sets up base paths for recursive content to resolve correctly.

API Endpoints

V1 Endpoints

EndpointPurpose
/v1/bsv/block/latestLatest block info
/v1/bsv/block/height/{h}Block by height
/v1/bsv/block/hash/{hash}Block by hash
/v1/bsv/tx/{txid}Raw transaction

V2 Endpoints

EndpointPurpose
/v2/tx/{txid}Raw transaction
/v2/tx/{txid}/proofMerkle proof
/v2/tx/{txid}/beefBEEF format proof
/v2/tx/{txid}/{vout}Specific output
/v2/block/tipLatest block header
/v2/chain/heightCurrent height
/v2/metadata/{outpoint}Inscription metadata
/v2/stream/{outpoint}Streaming content

DNS-Based Access

Map custom domains to inscriptions.

DNS TXT Record

Create _ordfs.yourdomain.com:

_ordfs.yourdomain.com IN TXT "ordfs=abc123..._0:5"

Format: ordfs={pointer}[:{sequence}]

How It Works

  1. User visits yourdomain.com/path/to/file
  2. ORDFS resolves DNS TXT record
  3. Returns content from inscription directory

Common Usage Patterns

Image Display

// Using bitcoin-image for normalization
import { getDisplayUrl } from "bitcoin-image";

const imageUrl = await getDisplayUrl("ord://abc123..._0");
// Returns: https://ordfs.network/abc123..._0

// Direct construction
const url = `https://ordfs.network/${txid}_${vout}`;

Fetch Content

// Get inscription content
const response = await fetch(`https://ordfs.network/${origin}`);
const content = await response.text();

// Get with metadata
const metaResponse = await fetch(
  `https://ordfs.network/content/${origin}?map=true`
);
const mapData = metaResponse.headers.get("X-Map");

Check Latest Version

// Get latest sequence
const response = await fetch(`https://ordfs.network/content/${origin}`);
const sequence = response.headers.get("X-Ord-Seq");
const currentOutpoint = response.headers.get("X-Outpoint");

Caching Behavior

Request TypeCache TTL
Specific sequence (:N)30 days
Latest sequence (default)60 seconds
Block headers (depth 100+)30 days
Block headers (depth 4-99)1 hour
Block tipNo cache

Additional Resources

Reference Files

  • references/api-reference.md - Complete API documentation
  • references/advanced-features.md - DNS, streaming, directories

Examples

  • examples/fetch-content.ts - Content fetching patterns
  • examples/recursive-inscription.html - Recursive inscription example

Related Packages

  • bitcoin-image - URL normalization for ordfs.network
  • @1sat/actions - Create inscriptions
  • @1sat/templates - Inscription templates

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

32.83%
按下载量换算48

Claude

30.17%
按下载量换算44

Cursor

18.12%
按下载量换算27

Gemini CLI

9.79%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills