Spiral gives your agent every tool with one account. Browse the tools →

Muse Code · Developer

How to Use Docker Hub publisher repositories in Muse Code

Returns repositories within a Docker Hub namespace, including descriptions and pull counts. Use it to survey a publisher's catalog before inspecting individual repositories.

Prompts to try with Docker Hub publisher repositories in Muse Code

Copy an example into Muse Code, or ask in your own words.

Use Docker Hub publisher repositories to look this up and give me the result as a table. Save the result in ./assets.

Docker Hub publisher repositoriesMuse Code
Try asking
  • Pull the latest numbers from Docker Hub publisher repositories and tell me what changed since last week.

  • Check Docker Hub publisher repositories and summarize what you find in three bullet points.

  • Pull the newest data from Docker Hub publisher repositories and give me the result as a table.

  • Check Docker Hub publisher repositories every morning and tell me only when something changed.

How to set up Docker Hub publisher repositories in Muse Code

Pick the way that suits you. Each takes about two minutes.

Use Spiral's MCP server

  1. Install Muse Code
    curl -fsSL https://dev.meta.ai/install.sh | bash
  2. Ask Muse to add the server

    Start muse and ask:

    Add the Spiral MCP server at https://api.spiral.ai/mcp
  3. Sign in

    In your terminal, run:

    muse mcp login spiral

Use the Spiral skill

  1. Send Muse Code this message

    Your agent reads Spiral's skill and sets itself up.

    set up https://spiral.ai/SKILL.md
  2. Sign in or paste a key

    Approve Spiral in the browser, or give the agent a key from the console.

Use the Spiral CLI

  1. Install and sign in

    Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

    npx -y spiral-cli@latest init

Call the Spiral API

  1. Create an API key

    In the console, under API keys.

  2. Run Docker Hub publisher repositories

    One request; the result comes back by polling or a webhook.

    curl https://api.spiral.ai/v1/runs \
      -H "Authorization: Bearer $SPIRAL_API_KEY" \
      -H "Content-Type: application/json" \
      -H "Idempotency-Key: $(uuidgen)" \
      -d '{
        "provider": "alexandria",
        "model": "hub-docker-com/container-images/list_namespace_repositories",
        "input": {
          "namespace": "<namespace>"
        }
      }'

Then paste one of the prompts above: Muse Code finds Docker Hub publisher repositories on Spiral, shows the price and runs it.

Docker Hub publisher repositories providers and prices

Spiral runs Docker Hub publisher repositories through Alexandria. Open a card for today's price, with every fee included.

AlexandriaDeveloper
Docker Hub · List namespace repositories
hub-docker-com/container-images/list_namespace_repositories

Settings you can ask for

Ask Muse Code for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Orderinglast_updated

last_updated: most recently pushed first. Omit for Docker Hub's default order.

Page size1 to 10025

Records per page (Docker Hub clamps anything above 100 to 100).

Every API field of Docker Hub · List namespace repositories is on its tool page: open its card above.

What can you do with Docker Hub publisher repositories in Muse Code?

Prepare an image change proposal with Docker Hub evidence beside the project's container references. A coding agent can turn repository documentation, publisher context, catalog categories, tags, and reported vulnerabilities into review notes.

Review a container publisher

Review Grafana's publisher profile and repository catalog, then read the documentation for relevant images. Compare those repositories with Grafana search results to distinguish the publisher's catalog from other matching entries.

Build an internal image directory

Organize selected public Grafana repositories under Docker Hub's categories. Include the publisher profile and available tags so developers can browse the catalog and investigate image versions.

Discover observability tools

Start with Docker Hub's categories and search for observability images. Review the profiles and repository catalogs of publishers such as Grafana to identify related tools for an evaluation.

Produce a publisher update digest

Compare saved Grafana repository and tag listings with current results each week. Organize the report by Docker Hub category and inspect changed tags for platform digests, sizes, and push dates.

Questions about Docker Hub publisher repositories in Muse Code

Can Muse Code use Docker Hub publisher repositories?

Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run Docker Hub publisher repositories like any built-in tool.

How much does Docker Hub publisher repositories cost in Muse Code?

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse Code plan is separate.

Do I need an Alexandria account to use Docker Hub publisher repositories in Muse Code?

No. Spiral runs Docker Hub publisher repositories on its own Alexandria account. You sign in to Spiral once and never paste a key.

How long does it take to set up Docker Hub publisher repositories in Muse Code?

About two minutes: install Muse Code, then ask Muse to add the server, then sign in.

Does Muse Code wait while Docker Hub publisher repositories runs?

Docker Hub publisher repositories runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.

Does public Docker Hub data include private repositories?

Public repositories are accessible to everyone. Private repositories require appropriate permissions, so a public publisher catalog does not establish everything that publisher stores.

Does one response contain every repository or tag?

Repository and tag listings are paginated. Docker Hub provides a total result count and a link to the next page when more results exist.

Can the same Docker Hub tag point to a different image later?

Yes. Docker Hub tags are mutable by default, and a publisher can change which image a tag references.

Can vulnerability counts change without another image push?

Yes. Docker Scout reevaluates stored image metadata as new vulnerability data becomes available, so an unchanged image can receive different findings.

Why can Docker Scout severity ratings differ from another scanner?

Scout prioritizes severity data from the vendor matching the package and version, such as Debian data for Debian packages. It falls back to NIST scoring when the vendor does not provide scoring data.

Get started

Start using Docker Hub publisher repositories in Muse Code

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Muse Code:

Set up Muse Code

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options