open-index/open-npm huggingface dataset:
npm package: @opensource-together/mcp
Description: MCP server for discovering open-source projects via OST Linker
Latest version: 0.1.0

# @opensource-together/mcp

> Need a project? Just ask your agent.

Stop browsing GitHub. Tell your AI agent what you need — it finds the right open-source project for you. Works with Claude, OpenClaw, and any MCP-compatible agent.

## Quick Start

Add this to your MCP client config:

```json
{
  "mcpServers": {
    "ost": {
      "command": "npx",
      "args": ["@opensource-together/mcp"]
    }
  }
}
```

## Tools

| Tool | What it does |
|------|-------------|
| `search_projects` | Search by keyword + filter by category, domain, or tech stack |
| `get_project` | Get full details on any project |
| `get_trending` | See what's hot right now |
| `find_similar` | Find similar projects using AI embeddings |
| `list_categories` | Browse all categories |
| `list_domains` | Browse all domains |
| `list_techstacks` | Browse all tech stacks |

## How it works

Ask your agent > [@ost-mcp](https://github.com/opensource-together/ost-mcp) > [@ost-linker](https://github.com/opensource-together/ost-linker) > projects found

- *"Find me React projects for e-commerce"*
- *"What's trending in open source right now?"*
- *"Show me projects similar to FastAPI"*

## Development

```bash
npm install
npm test
npm run build
npm run dev
```

## License

MIT
npm package: @opensource365/logging
Description: A lightweight and opensource logging library
Author: OpenSource365
Latest version: 1.0.7

# @opensource365/logging

A **lightweight**, **extensible**, and **framework-agnostic** logging library for TypeScript and JavaScript applications. Easily log structured messages to the console, files, APIs, or custom destinations with zero dependencies and full control.

---

## ✨ Features

- ✅ **Minimal & Fast** – Zero dependencies, no runtime bloat.
- 🔧 **Flexible Log Levels** – Support for Debug, Info, Warning, and Error.
- 📦 **Pluggable Providers** – Output logs to console, file, SharePoint List, or any custom implementation.
- 🎯 **Custom Formatters** – Override log formatting per provider.
- 🛠️ **Easy Integration** – Works in Node, browser, or serverless environments.
- 🔓 **Open Source** – MIT licensed.

---

## 📦 Installation

Install via npm:

```bash
npm install @opensource365/logging
```

---

## 🚀 Quick Start

```ts
import { Logger, LogLevel } from '@opensource365/logging';

// Add a console log provider with default formatting and level filtering
Logger.addConsole();

// Add a console log provider with custom formatting and level filtering
Logger.addConsole({
  minimumLogLevel: LogLevel.Information,
  formatMessage: (entry) => {
    const timestamp = new Date().toISOString();
    return `[${timestamp}] (${LogLevel[entry.level]}): ${entry.message}`;
  },
});

// Log various levels
Logger.info("This is an information message.");
Logger.error("This is an error message.");
Logger.warn("This is a warning message.");
Logger.debug("This debug message will not appear (level too low).");
```

---

## 🧩 Custom Providers

You can define and add your own logging provider by implementing the `ILogProvider` interface:

```ts
const fileProvider: ILogProvider = {
  log(entry) {
    // Send to file system, API, or wherever
    writeToFile(`[${LogLevel[entry.level]}] ${entry.message}`);
  }
};

Logger.addProviders(fileProvider);
```

---

## 🧼 Utility Methods

```ts
Logger.clearProviders(); // Removes all logging providers
Logger.getProviders();   // Returns current list of providers
```

---

## 📚 API Reference

### `ILogEntry`
```ts
interface ILogEntry {
  level: LogLevel;
  message: string;
  data?: any;
}
```

### `ILogProvider`
```ts
interface ILogProvider {
  log(entry: ILogEntry): void;
}
```

### `IConsoleLogOptions`
```ts
interface IConsoleLogOptions {
  minimumLogLevel?: LogLevel;
  formatMessage?: (entry: ILogEntry) => string;
}
```

---

## 🛡 License

MIT © [OpenSource365](https://opensource365.org)
npm package: @opensourceframework/critters
Description: Embedded CSS critical path extraction for Next.js applications
Author: OpenSource Framework Contributors
Latest version: 0.0.1

# @opensourceframework/critters

[![npm version](https://img.shields.io/npm/v/@opensourceframework/critters.svg)](https://www.npmjs.com/package/@opensourceframework/critters)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

> Embedded CSS critical path extraction for Next.js applications

This is a maintained fork of the original `critters` package, maintained by the OpenSource Framework community.

## Why This Fork?

The original package is no longer actively maintained. This fork provides:

- 🔄 **Active Maintenance**: Regular updates and bug fixes
- 📦 **Modern Tooling**: Built with TypeScript, tsup, and modern build tools
- 🔒 **Security**: Prompt security updates and vulnerability patches
- 📖 **Documentation**: Improved and up-to-date documentation
- 🧪 **Testing**: Comprehensive test coverage

## Installation

```bash
npm install @opensourceframework/critters
# or
yarn add @opensourceframework/critters
# or
pnpm add @opensourceframework/critters
```

## Usage

```javascript
// Example usage - will be updated when implementation is complete
import { /* exports */ } from '@opensourceframework/critters';
```

## Documentation

Full documentation will be available at [https://opensourceframework.dev/docs/critters](https://opensourceframework.dev/docs/critters)

## Contributing

We welcome contributions! Please see our [Contributing Guide](../../CONTRIBUTING.md) for details.

## License

MIT © OpenSource Framework Contributors

## Links

- [Original Package](https://www.npmjs.com/package/critters)
- [Issue Tracker](https://github.com/opensourceframework/opensourceframework/issues)
- [Changelog](./CHANGELOG.md)
npm package: @opensourceframework/docs-bot
Description: Documentation assistant for OpenSourceFramework packages
Author: OpenSource Framework Contributors
Latest version: 0.0.1

# @opensourceframework/docs-bot

A command-line documentation assistant for the OpenSourceFramework monorepo. It can answer questions about package APIs, usage, and best practices.

## Features (planned)

- Search package documentation and READMEs
- Provide code examples
- Explain configuration options
- Generate usage snippets

This is an initial scaffold. More to come.
npm package: @opensourceframework/next-mdx-toc
Description: Add table of contents to MDX
Author: OpenSource Framework Contributors
Latest version: 0.1.3

# next-mdx-toc

Add table of contents to MDX.

## Installation

```
npm i --save next-mdx-toc remark-slug remark-autolink-headings
```

## Usage

1. Retrieve the MDX node using `getMdxNode`:

```js
const doc = await getMdxNode("doc", context, {
  mdxOptions: {
    remarkPlugins: [
      require("remark-slug"),
      require("remark-autolink-headings"),
    ],
  },
})
```

2. Then call `getTableOfContents(node: MdxNode): TableOfContents`:

```js
const toc = await getTableOfContents(doc)
```

## Example

```jsx
import * as React from "react"
import { getMdxNode } from "next-mdx/server"
import { getTableOfContents } from "next-mdx-toc"

export default function Page({ doc, tableOfContents }) {}

export async function getStaticProps(context) {
  const doc = await getMdxNode("doc", context, {
    mdxOptions: {
      remarkPlugins: [
        require("remark-slug"),
        require("remark-autolink-headings"),
      ],
    },
  })

  return {
    props: {
      doc,
      tableOfContents: await getTableOfContents(doc),
    },
  }
}
```

## Render

To render the table of contents, use a recursive component type:

```tsx
import { TableOfContents } from "next-mdx-toc"

function Toc({ tree }: { tree: TableOfContents }) {
  return tree?.items.length ? (
    <ul>
      {tree.items.map((item) => {
        return (
          <li key={item.title}>
            <a href={item.url}>{item.title}</a>
            {item.items?.length ? <Toc tree={item} /> : null}
          </li>
        )
      })}
    </ul>
  ) : null
}
```

```tsx
<Toc tree={tableOfContents} />
```

## TypeScript

If you want to add the table of contents to your `MdxNode`, you can do so as follows:

```ts
import { TableOfContents } from "next-mdx-toc"
import { MdxNode } from "next-mdx/server"

interface Doc extends MdxNode {
  toc: TableOfContents
}
```

## License

Licensed under the [MIT license](https://github.com/shadcn/next-mdx/blob/master/LICENSE).
npm package: @opensourcejam/validador-cups
Description: Validador CUPS
Author: Kemil Beltre
Latest version: 0.0.4

# Validador Cups

Un módulo simple para validar un código
[CUPS](https://es.wikipedia.org/wiki/C%C3%B3digo_Unificado_de_Punto_de_Suministro)

## Ejemplo

**JavaScript**

```javascript
const { cups } = require('validador-cups')

const isValid = cups.validate('ES002100000123456789AB') // false
```

**TypeScript**

```typescript
import { cups } from 'validador-cups'

const isValid = cups.validate('ES002100000123456789AB') // false
```

## Licencia

Este proyecto está bajo la Licencia MIT. Consulta el archivo [LICENSE](./LICENSE) para obtener más detalles
npm package: @opensourceregistry/npm-test-package
Description: The OpenSource Registry's NPM verification test package
Latest version: 1.0.5

[opensourceregistry_package_id]: # (f7a71a516657247cc768e8ea4983785e77bf31bcd09680155c95cad37ef15606)
# NPM test package

This NPM package is used as a test package to verify package verification on the OpenSource Registry.
npm package: @opensourcerist/nexgen-cli
Description: This library was generated with [Nx](https://nx.dev).
Latest version: 1.0.32

# nexgen-cli

This library was generated with [Nx](https://nx.dev).

## Running unit tests

Run `nx test nexgen-cli` to execute the unit tests via [Jest](https://jestjs.io).

## Running lint

Run `nx lint nexgen-cli` to execute the lint via [ESLint](https://eslint.org/).
npm package: @opensourcewtf/dojo
Description: Dojo Skill Manager CLI - A package manager for AI agent skills
Author: OpenSourceWTF
Latest version: 0.1.2

# @opensourcewtf/dojo

> CLI for managing AI agent skills

[![npm version](https://img.shields.io/npm/v/@opensourcewtf/dojo.svg)](https://www.npmjs.com/package/@opensourcewtf/dojo)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

## Install

```bash
npm install -g @opensourcewtf/dojo
```

## Usage

```bash
# Search for skills
dojo search testing

# Install a skill
dojo learn @anthropics/create-docx

# Install specific version
dojo learn @anthropics/create-docx@1.0.0

# List installed skills
dojo list

# Sync across agents
dojo sync

# Remove a skill
dojo unlearn create-docx
```

## Supported Agents

Skills are installed to all detected agent directories:

| Agent | Directory | Format |
|-------|-----------|--------|
| Claude | `.claude/skills/*.md` | Markdown |
| Gemini | `.agent/workflows/*.md` | Markdown |
| Cursor | `.cursor/rules/{skill}/RULE.md` | Folder + frontmatter |

## API

```typescript
import { learn } from '@opensourcewtf/dojo';

await learn('@anthropics/create-docx', {
  registryPath: './registry'
});
```

## License

[MIT](../../LICENSE) © OpenSourceWTF
npm package: @opensourcewtf/dojo-mcp
Description: Dojo Skill Manager MCP Server - Model Context Protocol server for AI agent skill discovery
Author: OpenSourceWTF
Latest version: 0.1.2

# @opensourcewtf/dojo-mcp

> MCP server for natural language AI skill discovery

[![npm version](https://img.shields.io/npm/v/@opensourcewtf/dojo-mcp.svg)](https://www.npmjs.com/package/@opensourcewtf/dojo-mcp)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

## Install

```bash
npm install @opensourcewtf/dojo-mcp
```

## MCP Configuration

### Claude Desktop

Add to `~/.config/claude/claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "dojo": {
      "command": "npx",
      "args": ["-y", "@opensourcewtf/dojo-mcp"]
    }
  }
}
```

### Gemini CLI

Add to your Gemini MCP settings:

```json
{
  "mcpServers": {
    "dojo": {
      "command": "npx",
      "args": ["-y", "@opensourcewtf/dojo-mcp"]
    }
  }
}
```

### Local Development

```json
{
  "mcpServers": {
    "dojo": {
      "command": "node",
      "args": ["/absolute/path/to/dojo/packages/mcp/dist/index.js"]
    }
  }
}
```

## Tool: `dojo_learn`

Installs skills to detected AI agent directories.

```
Name: dojo_learn
Description: Learn a new skill when user asks "do you know X", "teach me X", or "learn X"
```

### Input Schema

```json
{
  "skill": "string (required) - Skill name or search term",
  "version": "string (optional) - Version or commit hash",
  "projectRoot": "string (optional) - Project root for installation"
}
```

### Example Triggers

- "Do you know how to create Word documents?"
- "Teach me testing"
- "Learn the debugging skill"

## Tool: `dojo_unlearn`

Removes skills from detected AI agent directories.

```
Name: dojo_unlearn
Description: Remove a skill when user asks to "unlearn", "forget", or "remove" a skill
```

### Input Schema

```json
{
  "skill": "string (required) - Skill name to remove",
  "projectRoot": "string (optional) - Project root for removal"
}
```

### Example Triggers

- "Unlearn the testing skill"
- "Forget frontend-design"
- "Remove the debugging skill"

## API

```typescript
import { server, handleDojoLearn, handleDojoUnlearn, TOOLS } from '@opensourcewtf/dojo-mcp';

// Access tool definitions
console.log(TOOLS);

// Handle learn requests programmatically
const result = await handleDojoLearn({ skill: 'testing', projectRoot: '/path/to/project' });

// Handle unlearn requests programmatically
const result = await handleDojoUnlearn({ skill: 'testing', projectRoot: '/path/to/project' });
```

## License

[MIT](../../LICENSE) © OpenSourceWTF
npm package: @opensourcewtf/waaah-cli
Description: Command-line interface for WAAAH local testing and scripting
Latest version: 0.1.0

# @opensourcewtf/waaah-cli

Command-line interface for local testing and interaction with the WAAAH system.

## Environment Variables

| Variable | Default | Description |
|----------|---------|-------------|
| `WAAAH_SERVER_URL` | `http://localhost:3000` | Server URL |
| `WAAAH_API_KEY` | (none) | API key for authentication |

## Usage

```bash
# Set environment
export WAAAH_SERVER_URL=http://localhost:3000
export WAAAH_API_KEY=your_key

# Interactive mode (async, background listener)
pnpm cli

# Send a task
pnpm cli send fullstack-1 "Implement the login page"

# Send with priority
pnpm cli send fullstack-1 "Fix critical bug" --priority high

# List agents
pnpm cli list-agents

# Check agent status
pnpm cli status fullstack-1

# Debug server state
pnpm cli debug
```

## Commands

| Command | Description |
|---------|-------------|
| `send <target> <prompt>` | Send task to agent |
| `list-agents` | List registered agents |
| `status <agentId>` | Get agent status |
| `debug` | Show server debug info |
npm package: @opensourcewtf/waaah-mcp-proxy
Description: Stdio↔HTTP bridge for connecting AI agents to WAAAH
Latest version: 0.1.0

# @opensourcewtf/waaah-mcp-proxy

A bridge that connects a local autonomous agent (via `stdio`) to the remote WAAAH MCP server (via HTTP).

## Installation

```bash
# Global install
npm install -g @opensourcewtf/waaah-mcp-proxy

# Or use directly with npx
npx @opensourcewtf/waaah-mcp-proxy
```

## How it Works

1.  Starts as a local MCP server using Stdio transport.
2.  Connects to your LLM client (e.g., Antigravity, Claude Desktop).
3.  Proxies tool calls (`register_agent`, `wait_for_prompt`, etc.) to the central server.
4.  Provides fallback identity if not specified in tool calls.

## Environment Variables

| Variable | Default | Description |
|----------|---------|-------------|
| `WAAAH_SERVER_URL` | `http://localhost:3000` | Server URL (required) |
| `WAAAH_API_KEY` | (none) | API key for authentication |
| `AGENT_ID` | `unknown-agent` | Fallback agent ID (optional) |
| `AGENT_ROLE` | `developer` | Fallback agent role (optional) |

> **Note:** `AGENT_ID` and `AGENT_ROLE` are **fallback defaults only**. When using workflow prompts (e.g., `/waaah-fullstack`), the workflow explicitly specifies the agent identity in `register_agent()` calls, overriding these environment variables.

## MCP Client Configuration

Add to your MCP client settings (e.g., `~/.gemini/antigravity/mcp_config.json`):

```json
{
  "mcpServers": {
    "waaah": {
      "command": "npx",
      "args": ["@opensourcewtf/waaah-mcp-proxy"],
      "env": {
        "WAAAH_SERVER_URL": "http://localhost:3000",
        "WAAAH_API_KEY": "your_api_key"
      }
    }
  }
}
```

The agent identity is determined by the workflow you invoke:
- `/waaah-fullstack` → registers as `fullstack-1` (Full Stack Engineer)
- `/waaah-testeng` → registers as `test-1` (Test Engineer)
- `/waaah-pm` → registers as `pm-1` (Project Manager)

## Local Development

```bash
pnpm build
node dist/index.js
```
npm package: @opensourcewtf/waaah-mcp-server
Description: Central MCP orchestration server for WAAAH with Admin Dashboard
Latest version: 0.1.0

# @opensourcewtf/waaah-mcp-server

The core orchestration engine for the WAAAH system. Manages agent registration, task queuing, and tool execution.

## Features

- **Agent Registry**: SQLite-backed tracking of agents, capabilities, and aliases.
- **Task Queue**: Priority-based persistent queue with ACK-based delivery.
- **MCP Tools**: Standard WAAAH toolset via HTTP endpoints.
- **Admin API**: Endpoints for task management.
- **API Key Auth**: Optional authentication via `WAAAH_API_KEY`.

## Environment Variables

| Variable | Default | Description |
|----------|---------|-------------|
| `PORT` | `3000` | Server listen port |
| `WAAAH_PORT` | `3000` | Alias for PORT |
| `WAAAH_API_KEY` | (none) | Shared secret for API authentication |
| `AGENTS_CONFIG` | `./config/agents.yaml` | Path to agent configuration |
| `DB_PATH` | `./data/waaah.db` | SQLite database path |

## Local Development

```bash
pnpm build
node dist/server.js
```

## Docker

The server is designed to run via Docker Compose. See the root `docker-compose.yml`.

```bash
docker compose up waaah-server
```

## Tools Exposed

| Tool | Action |
|------|--------|
| `register_agent` | Register identity and capabilities |
| `wait_for_prompt` | Long-poll for new tasks |
| `send_response` | Submit task results/status |
| `assign_task` | Delegate tasks to peers |
| `list_agents` | Discovery of available agents |
| `get_agent_status` | Check peer availability |
| `admin_update_agent` | Update agent name/color |
npm package: @opensourcewtf/waaah-types
Description: Shared TypeScript definitions and Zod schemas for WAAAH
Latest version: 0.1.0

# @opensourcewtf/waaah-types

Shared TypeScript definitions, schemas, and interfaces for the WAAAH system.

## Contents

- **Agent Types**: `AgentIdentity`, `AgentRole`
- **Task Types**: `Task`, `TaskStatus`, `TaskPriority`
- **MCP Schemas**: Zod definitions for tool arguments (`AssignTaskArgs`, `RegisterAgentArgs`, etc.)

## Usage

```typescript
import { Task, AgentRole } from '@opensourcewtf/waaah-types';
```
npm package: @openspec-opc/codex-plugin
Description: Codex runtime guard plugin for OpenSpec OPC workflows.
Latest version: 0.2.0

# codex-spec-opc

`codex-spec-opc` is the Codex-facing local plugin scaffold for OpenSpec OPC.

It currently reuses:

- the shared TypeScript guard core in [`opc-guard-core`](../../packages/opc-guard-core/)
- the Codex adapter/runtime/plugin implementation in this directory's `dist/`

## What exists

- `.codex-plugin/plugin.json` with concrete plugin metadata
- `hooks/index.mjs` that exposes `createPlugin`, `install`, and `register`
- `hooks.json` pointing at the local hook bridge entry

## Current limitation

The exact Codex local plugin hook manifest format has not been verified against
official runtime docs yet. `hooks.json` is therefore a provisional contract for
this repository's scaffold work, not a claim that the current Codex runtime
already consumes this file shape verbatim.

As of April 6, 2026, the official OpenAI docs we could verify cover:

- Codex product overview
- Docs MCP setup for Codex
- local shell / tool execution patterns

But they do not document a public, stable local plugin manifest format matching
this repository's `.codex-plugin/plugin.json` plus `hooks.json` shape.

References:

- https://platform.openai.com/docs/codex
- https://platform.openai.com/docs/docs-mcp
- https://platform.openai.com/docs/guides/tools-local-shell

## Integration direction

The intended runtime path is:

`codex-spec-opc/hooks/index.mjs`
-> `codex-spec-opc/dist/codex-plugin.js`
-> `codex-spec-opc/dist/codex-runtime.js`
-> shared OpenSpec OPC guard core
npm package: @opensrp/ant-icons
Description: Ant Design + Material Design Icon
Author: Fede Ramirez
Latest version: 0.0.1

# Ant design icons

[![GitHub Release](https://img.shields.io/github/v/release/2fd/ant-design-icons?sort=semver)](https://github.com/2fd/ant-design-icons/releases)
[![NPM Release](https://img.shields.io/npm/v/@2fd/ant-design-icons)](https://www.npmjs.com/package/@2fd/ant-design-icons)

![ant-design-icons](./static/ant-design-icons.png)

[Ant Design](https://ant.design/) + [Material Design Icon](https://materialdesignicons.com/) = [Ant Design Icon](http://2fd.github.io/ant-design-icons)

## install

```bash
  npm install --save @2fd/ant-design-icons
```

```bash
  yarn add @2fd/ant-design-icons
```

## find

Search the icon that you need in the homepage: [`http://2fd.github.io/ant-design-icons`](http://2fd.github.io/ant-design-icons) **More than 5000!**

## use

```typescript
import React from 'react'
import CodeTagsIcon from '@2fd/ant-design-icons/lib/CodeTagsIcon'

export default function MyComponent() {
  return <CodeTagsIcon />
}
```